From: Leslie P. P. <sk...@vi...> - 2009-02-17 15:51:18
|
I have a spawned thread that will not stop running (although it should). Is there a way to interrupt it (like I can with the currently active foreground thread by sending SIGINT to it) and get into the debugger, so I can take a look at the call stack of the current execution? Leslie -- LinkedIn Profile: http://www.linkedin.com/in/polzer Xing Profile: https://www.xing.com/profile/LeslieP_Polzer Blog: http://blog.viridian-project.de/ |
From: Kalyanov D. <kal...@gm...> - 2009-02-17 16:01:15
|
On Tuesday 17 February 2009 18:51:11 Leslie P. Polzer wrote: > I have a spawned thread that will not stop running (although it should). > > Is there a way to interrupt it (like I can with the currently active > foreground thread by sending SIGINT to it) and get into the debugger, > so I can take a look at the call stack of the current execution? You can list all threads with (sb-thread:list-all-threads) and with the thread object there. Once you have the thread object, call (sb-thread:interrupt-thread thread (lambda () (break)) and you should get to the debugger. |
From: Tobias C. R. <tc...@fr...> - 2009-02-17 16:01:39
|
"Leslie P. Polzer" <sk...@vi...> writes: > I have a spawned thread that will not stop running (although it should). > > Is there a way to interrupt it (like I can with the currently active > foreground thread by sending SIGINT to it) and get into the debugger, > so I can take a look at the call stack of the current execution? > > Leslie M-x slime-list-threads, then `d'. -T. |