On Tue, 2011-05-10 at 11:02 +0200, Richard Braun wrote: > On Tue, May 10, 2011 at 10:53:00AM +0200, Svante Signell wrote: > > On Tue, 2011-05-10 at 10:11 +0200, Richard Braun wrote: > > > What makes you think there are two signal threads ? > > > > Did you look at the pasted output? > > Are you serious asking that ?
Sorry, but your question was not referring to the pasted code at all, just a direct question. You know better than me of course, I'm just trying to understand things and admittedly do some guess work. > > (gdb) thread apply all bt > > > > Thread 6 (Thread 19821.6): .. > > #2 0x01195608 in timer_thread () at ../sysdeps/mach/hurd/setitimer.c:91 > > Cannot access memory at address 0x2a000 > I just see threads calling mach_msg() ... One seems to be related to > POSIX timers (timer_thread) and the other is a POSIX thread receiving > a message. I'm not even sure you can see the signal thread with gdb > (I'll check that). So, again, what makes you think there are two signal > threads ? See above. BTW: What is triggering a new thread, a fork or? Can you explain why thread number 6 points to an invalid memory address? -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1305018809.4698.193.ca...@s1499.it.kth.se
