Date: Mon, 16 May 2005 14:18:30 -0700 From: Chris Pressey <cpressey@catseye.mine.nu> To: freebsd-hackers@freebsd.org Subject: Re: Console ASCII interpretation Message-ID: <20050516141830.6d0ea55e.cpressey@catseye.mine.nu> In-Reply-To: <20050516171143.GA19979@skatecity> References: <20050516171143.GA19979@skatecity>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 16 May 2005 19:11:44 +0200 alexander <arundel@h3c.de> wrote: > Hi there. > > I'm using syscall number 4 write() to output data to stdout using x86 > assembly. When I try to output the following DWORD: 0x00003532 I get > the following output under Eterm and xterm: "25". Which is exactly > what I want. > > However when I do the very same under the console (using bash or sh. > It doesn't matter) I get this output: "25 ". > > I looked up the ASCII value for 00h and it says NUL. Doesn't that mean > that there shouldn't be any output at all? syscons and xterm implement different terminal emulations. xterm attempts to be compatible with a DEC VT102 and/or VT220, which treat NUL as non-printing. syscons doesn't aim to be compatible with anything in particular (so there is no standard to which it can be held to for rendering NUL as a blank space.) See the respective manual pages for more information. -Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050516141830.6d0ea55e.cpressey>