This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/14135] Fails in gdb.python/py-finish-breakpoint.exp when`set target-async on'.
- From: "kevin.pouget at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 23 May 2012 10:58:17 +0000
- Subject: [Bug gdb/14135] Fails in gdb.python/py-finish-breakpoint.exp when`set target-async on'.
- Auto-submitted: auto-generated
- References: <bug-14135-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14135
--- Comment #3 from Kevin Pouget <kevin.pouget at gmail dot com> 2012-05-23 10:58:17 UTC ---
you're right indeed, I did not notice this part of the execution.
> The doc says "23.2.2.20 Manipulating breakpoints using Python. ... You should
> not alter the execution state of the inferior (i.e., step, next, etc.), alter
> the current frame context (i.e., change the current active frame), or alter,
> add or delete any breakpoint. As a general rule, you should not alter any data
> within gdb or the inferior at this time.".
> I doubt "where 1" falls in this category in async mode.
I'm not sure to understand your position here: would you like me to change
appropriately "gdb.execute ("where 1")" and fix the testsuite failure, or will
you guys try to fix the underlying problem ?
--
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.