[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Race condition (was problem) in Mach/Hurd?

From: Svante Signell
Subject: Re: Race condition (was problem) in Mach/Hurd?
Date: Tue, 10 May 2011 11:13:29 +0200

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?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]