This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug python/12930] GDB state during gdb.Breakpoint::stop callback isunclear
- From: "pedro at codesourcery dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 24 Jun 2011 13:53:32 +0000
- Subject: [Bug python/12930] GDB state during gdb.Breakpoint::stop callback isunclear
- Auto-submitted: auto-generated
- References: <bug-12930-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12930
--- Comment #2 from Pedro Alves <pedro at codesourcery dot com> 2011-06-24 13:53:01 UTC ---
"attach" is a synchronous command. You've effectively nested an event loop
within your "stop" callback (you'll see wait_for_inferior twice in the
backtrace). The topmost wait_for_inferior will switch _all_ threads' state to
stopped when it finishes...
These scenarios make my head hurt with non-stop/async on...
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.