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] |
Hi Daniel, please commit if appropriate: Created the attached minimal patch fixing the gdb lockup. 2006-07-22 Jan Kratochvil <jan.kratochvil@redhat.com> * linux-thread-db.c (thread_db_wait): Avoid locking up on stale threading state after TARGET_WAITKIND_EXECD. No testsuite case, waiting on MAY_FOLLOW_EXEC resolution below. On Fri, 21 Jul 2006 20:44:21 +0200, Daniel Jacobowitz wrote: ... > Turning on MAY_FOLLOW_EXEC is not a good idea. No one really knows how > that behavior works, a lot of it doesn't, and the way it implicitly > changes the symbol file is very disorienting. Please don't mix it up > with the fix for your current bug. Still I am for MAY_FOLLOW_EXEC as it improves the user experience and makes debugging of exec()ing processes much more convenient - without having to find out how each child gets executed and replay such conditions by hand. As gdb-6.5 has been released and the MAY_FOLLOW_EXEC feature IMO generally works for GNU/Linux - isn't appropriate to enable it and settle it down? I would even like to fix any issues possibly roaring its head. Regards, Jan
Attachment:
gdb-cvs20060722-exec_reset.patch
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |