Hi Derek,<br><br><div class="gmail_quote">On Thu, Jul 22, 2010 at 2:25 PM, Derek O'Connell <span dir="ltr"><<a href="mailto:doconnel@gmail.com">doconnel@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
On 22/07/10 22:20, Eliot Miranda wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
<br>
<br>
Hi Paul,<br>
<br>
On Thu, Jul 22, 2010 at 2:14 PM, Paul DeBruicker<<a href="mailto:pdebruic@gmail.com" target="_blank">pdebruic@gmail.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Hi Eliot,<br>
<br>
<br>
<br>
On 07/22/2010 05:02 PM, <a href="mailto:vm-dev-request@lists.squeakfoundation.org" target="_blank">vm-dev-request@lists.squeakfoundation.org</a> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
handle SIGUSR2 nostop noprint noignore<br>
<br>
<br>
</blockquote>
If I include the above line in my .gdbinit then gdb complains:<br>
<br>
Cannot find user-level thread for LWP XXXXX<br>
<br>
where XXXXX is the process number for the VM. Sometimes the VM window<br>
stays open and freezes at that point and sometimes it closes. Gdb then<br>
states that the "Target is running" when I type in the commands you listed.<br>
If I comment the "handle SIGUSR2 ..." line out then I get this from those<br>
commands:<br>
<br>
</blockquote>
<br>
just looks like the OS/run-time is not letting the program set a handler for<br>
SIGUSR2 and/or not allowing it to be caught. This is a deal breaker. Why<br>
it's happening I don't know, but currently Cog's heartbeat on linux depends<br>
on being able to catch SIGUSR2.<br>
</blockquote>
<br></div>
From: <a href="http://pauillac.inria.fr/~xleroy/linuxthreads/faq.html" target="_blank">http://pauillac.inria.fr/~xleroy/linuxthreads/faq.html</a><br>
<br>
H.4: With LinuxThreads, I can no longer use the signals SIGUSR1 and SIGUSR2 in my programs! Why?<br>
<br>
The short answer is: because the Linux kernel you're using does not support realtime signals.<br></blockquote><div><br></div><div>I'd forgotten all that! I thought that stuff was ancient history. So we need two things, one is a pair of alternative signals, the other is a reliable #define that we can use to distinguish l'ancien regime from the modern day.</div>
</div><br><div>thanks Derek!</div><div><br></div><div>best</div><div>Eliot</div>