This is the mail archive of the gdb-prs@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]

[Bug gdb/14135] Fails in gdb.python/py-finish-breakpoint.exp when`set target-async on'.


http://sourceware.org/bugzilla/show_bug.cgi?id=14135

--- Comment #4 from Yao Qi <qiyao at gcc dot gnu.org> 2012-05-23 11:12:26 UTC ---
(In reply to comment #3)
> 
> 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 ?

I am not sure on this either :)  It is good if we can fix the underlying
problem, but don't know how much work it needs.  At the same time, I'd like to
remove "gdb.execute ("where 1")" from test case.  I am not familiar with
gdb/python, but the `stop' method is similar to breakpoint condition, and I
feel it is not right to put gdb.execute (which is similar to breakpoint action)
to it.

Anyway, I'll post a patch to @gdb-patches to see how people there think on
this.

-- 
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.


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