From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Sun, 13 Feb 2011 20:40:08 -0800 Message-ID: From: ron minnich To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] ratrace problem; debuggers welcome Topicbox-Message-UUID: ae068280-ead6-11e9-9d60-3106f5b1d025 On Sun, Feb 13, 2011 at 7:50 PM, erik quanstrom wro= te: > at least from the source i have, writing to p->hang after > the fork isn't going to do anything. =A0p->hang is only consulted > in sysexec. =A0i 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