On Sun, Feb 13, 2011 at 7:50 PM, erik quanstrom <quans...@quanstro.net> wrote:
> at least from the source i have, writing to p->hang after > the fork isn't going to do anything. p->hang is only consulted > in sysexec. i think you need to add the same test in sysfork. It is only supposed to be consulted in sysexec. Hang just means that the next exec will result in a stop, not the fork. You really only want to look for the hang when exec is called. In fact the parent can call exec -- even before a fork -- and the child will halt in the exec. Very handy. > it turns out that printing "." instead of the character for > non-ascii is unworkable for some things. I made a bad mistake there. Let's pick some sort of standard format and go with it. Here's my suggestion. Non-printable characters will be printed as \xx where xx is the hex code. '\' is considered a non-printable character because we don't want to get confused. Does that work for people? ron
