Re: sigint (was Re: [Sbcl-devel] cmucl (sbcl) doc patch?)

[William H. N. <wil...@ai...>]

On Mon, Nov 27, 2000 at 10:54:07AM +0100, ma...@at... wrote:
[test case, thank you] 
> I've been looking at this, but I haven't found a real solution up to
> now.
> I've appended a patch that will at least print the floating point
> exception,
> but it still hangs with the UNPRINTABLE-OBJECT.
> (I cleaned up some FIXMEs in debug-int, too).

Thanks for the patch. I'll apply the patch after I test the bigger
patch from your other message.

After that, perhaps tomorrow, I'll probably release the current system
as sbcl-0.6.9, flaky signal handling and all. Enough fixes have
accumulated that it's time to stop sitting on it.

Thanks also for the test cases. Soon I should take another shot at
understanding the signal handling problem. The last time I tried this
I ended up reading a lot of Linux kernel sources trying unsuccessfully
to understand what part of the state might not be being saved. Perhaps
with a better test case I can do some experiments to find out what
part of the state is not being saved.

One final thing: the quoted text above illustrates the way your
messages appear when they arrive in my mailbox, with extra line breaks
added in long lines. It's no problem for ordinary text, but when extra
line breaks are added in your patches, it's a minor nuisance. If by
any chance the extra line breaks are being added on your system, it
would be helpful if you'd turn them off. However, don't worry about it
too much. I'm in the habit of proof-reading patches anyway, and the
--dry-run option to patch tends to catch anything I overlook, so it's
really not a serious problem. (And for all I know, the problem is on
some intermediate system, or even on my system. What I know about mail
handling could be displayed in on a PDA in a rather large font..)

-- 
William Harold Newman <wil...@ai...>
software consultant
PGP key fingerprint 85 CE 1C BA 79 8D 51 8C  B9 25 FB EE E0 C3 E5 7C