From: Cyrus H. <ch...@bo...> - 2005-10-20 03:13:52
|
Dear sbcl-devel, In 0.9.5.76, we now test whether or not nodefer works using a SIGTRAP. While this works fine under normal circumstances on Mac OS, it breaks GDB. Gabor suggested the obvious fix of changing the signal under Darwin and this patch does that. It is a rather trivial and obvious patch, but it restores the ability to debug sbcl using gdb under Mac OS. I should offer the caveat that I really don't understand signals that well and don't know if this restores the intended behavior of the test, but it, at least, restores my ability to run sbcl using gdb. Thank you for considering this patch, Cyrus Index: sbcl/src/runtime/interrupt.c =================================================================== RCS file: /cvsroot/sbcl/sbcl/src/runtime/interrupt.c,v retrieving revision 1.102 diff -u -r1.102 interrupt.c --- sbcl/src/runtime/interrupt.c 17 Oct 2005 10:58:30 -0000 1.102 +++ sbcl/src/runtime/interrupt.c 20 Oct 2005 03:09:18 -0000 @@ -1075,8 +1075,13 @@ sa.sa_sigaction = sigaction_nodefer_test_handler; sigemptyset(&sa.sa_mask); sigaddset(&sa.sa_mask, SIGABRT); +#ifdef LISP_FEATURE_DARWIN + sigaction(SIGUSR1, &sa, NULL); + kill(getpid(), SIGUSR1); +#else sigaction(SIGTRAP, &sa, NULL); kill(getpid(), SIGTRAP); +#endif while (sigaction_nodefer_works == -1); } |
From: <me...@ho...> - 2005-10-21 07:27:31
|
On Thursday 20 October 2005 05:13, Cyrus Harmon wrote: > Dear sbcl-devel, > > In 0.9.5.76, we now test whether or not nodefer works using a > SIGTRAP. While this works fine under normal circumstances on Mac OS, > it breaks GDB. Gabor suggested the obvious fix of changing the signal > under Darwin and this patch does that. It is a rather trivial and > obvious patch, but it restores the ability to debug sbcl using gdb > under Mac OS. I should offer the caveat that I really don't > understand signals that well and don't know if this restores the > intended behavior of the test, but it, at least, restores my ability > to run sbcl using gdb. Thank you. Committed a similar patch in 0.9.5.78 that uses SIGINT.=20 Please consider screaming if it doesn't work. Cheers, G=E1bor. |
From: Cyrus H. <ch...@bo...> - 2005-11-10 16:37:40
|
SCREAM! Argg.... I should have checked this sooner, but SIGINT =20 doesn't work either. SIGUSR1 seems to work on Darwin, but SIGTRAP and =20= SIGINT don't. Not sure why not. It's easy enough to fix in versions I =20= need to debug, but we should probably check in a Darwin specific hack =20= so this doesn't bite others. Sorry to be the bearer of late bad news. Cyus On Oct 21, 2005, at 12:27 AM, G=E1bor Melis wrote: > On Thursday 20 October 2005 05:13, Cyrus Harmon wrote: >> Dear sbcl-devel, >> >> In 0.9.5.76, we now test whether or not nodefer works using a >> SIGTRAP. While this works fine under normal circumstances on Mac OS, >> it breaks GDB. Gabor suggested the obvious fix of changing the signal >> under Darwin and this patch does that. It is a rather trivial and >> obvious patch, but it restores the ability to debug sbcl using gdb >> under Mac OS. I should offer the caveat that I really don't >> understand signals that well and don't know if this restores the >> intended behavior of the test, but it, at least, restores my ability >> to run sbcl using gdb. > > Thank you. Committed a similar patch in 0.9.5.78 that uses SIGINT. > Please consider screaming if it doesn't work. > > Cheers, G=E1bor. > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, =20 > discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > Sbcl-devel mailing list > Sbc...@li... > https://lists.sourceforge.net/lists/listinfo/sbcl-devel |
From: <me...@ho...> - 2005-11-16 09:48:37
|
On Thursday 10 November 2005 17:37, Cyrus Harmon wrote: > SCREAM! Argg.... I should have checked this sooner, but SIGINT > doesn't work either. SIGUSR1 seems to work on Darwin, but SIGTRAP and > SIGINT don't. Not sure why not. It's easy enough to fix in versions I > need to debug, but we should probably check in a Darwin specific hack > so this doesn't bite others. Sorry to be the bearer of late bad news. =46ixed in 0.9.6.46. Cheers, G=E1bor |