This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Should this be on the blocker list for the 7.10 release?


> I filed this bug recently:
> 
> https://sourceware.org/bugzilla/show_bug.cgi?id=18600
> 
> In short, gdb sometimes leaves stopped newly spawned threads created by a
> fork child.  The "sometimes" happens quite often, so it's very easy to
> reproduce.  This has the effect of leaving (part) of your program stopped
> while you expect it to be running.  "info threads" shows the threads as
> running while in reality they aren't.
> 
> Is this bug serious enough to be on the blocking list for 7.10?  I would
> think so, as it's a regression compared to 7.9.  However, I don't want
> to impose work on anybody (e.g. Pedro, or anybody else familiar with the
> linux-nat subsystem), which is why I am asking.  I am willing to put time
> on this, but the chances of me successfully fixing the bug are quite slim.

Not sure. I think Pedro would be in a better position to answer.
For now, I've put this issue as a "maybe" for 7.10; so we will not
release until this is fixed, or we explicitly decide it's OK for 7.10.

Pedro?

-- 
Joel


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]