public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug python/13473] New: step N/next N does not trigger gdb.events.stop
@ 2011-12-06 22:19 khooyp at cs dot umd.edu
2011-12-06 22:37 ` [Bug python/13473] " khooyp at cs dot umd.edu
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: khooyp at cs dot umd.edu @ 2011-12-06 22:19 UTC (permalink / raw)
To: gdb-prs
http://sourceware.org/bugzilla/show_bug.cgi?id=13473
Bug #: 13473
Summary: step N/next N does not trigger gdb.events.stop
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: python
AssignedTo: unassigned@sourceware.org
ReportedBy: khooyp@cs.umd.edu
Classification: Unclassified
Created attachment 6091
--> http://sourceware.org/bugzilla/attachment.cgi?id=6091
Fix "step N"/"next N" to trigger gdb.events.stop at breakpoints.
When using the "step N"/"next N" command (where N is given), and the program
stops before N due to a breakpoint, no events seem to be posted to
gdb.events.stop in Python. For example, for the following program:
int foo(int x) {
x++;
return x;
}
int main(void) {
int i;
for (i = 0; i < 4000; i++) {
i = foo(i);
}
return 0;
}
The following transcript, run under GDB HEAD (as of Dec. 6, 2011), shows that
gdb.events.stop are not triggered for breakpoints:
(gdb) start
Temporary breakpoint 1 at 0x80483a6: file loop.c, line 9.
Starting program: /home/khooyp/tmp/loop
Temporary breakpoint 1, main () at loop.c:9
9 for (i = 0; i < 4000; i++) {
(gdb) py def foo(s): print s
(gdb) py gdb.events.stop.connect(foo)
(gdb) b foo
Breakpoint 2 at 0x8048397: file loop.c, line 3.
(gdb) step 100
Breakpoint 2, foo (x=0) at loop.c:3
3 x++;
(gdb) next 100
Breakpoint 2, foo (x=2) at loop.c:3
3 x++;
I've attached a patch that fixes this problem. The patch leads to the following
transcript, which shows the breakpoint events being posted:
... as before ...
(gdb) step 100
Breakpoint 2, foo (x=0) at loop.c:3
3 x++;
<gdb.BreakpointEvent object at 0xb6ef6190>
(gdb) next 100
Breakpoint 2, foo (x=2) at loop.c:3
3 x++;
<gdb.BreakpointEvent object at 0xb6ef6190>
--
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug python/13473] step N/next N does not trigger gdb.events.stop
2011-12-06 22:19 [Bug python/13473] New: step N/next N does not trigger gdb.events.stop khooyp at cs dot umd.edu
@ 2011-12-06 22:37 ` khooyp at cs dot umd.edu
2012-01-03 21:55 ` tromey at redhat dot com
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: khooyp at cs dot umd.edu @ 2011-12-06 22:37 UTC (permalink / raw)
To: gdb-prs
http://sourceware.org/bugzilla/show_bug.cgi?id=13473
Khoo Yit Phang <khooyp at cs dot umd.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |khooyp at cs dot umd.edu
--
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug python/13473] step N/next N does not trigger gdb.events.stop
2011-12-06 22:19 [Bug python/13473] New: step N/next N does not trigger gdb.events.stop khooyp at cs dot umd.edu
2011-12-06 22:37 ` [Bug python/13473] " khooyp at cs dot umd.edu
@ 2012-01-03 21:55 ` tromey at redhat dot com
2012-01-04 10:47 ` alves.ped at gmail dot com
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: tromey at redhat dot com @ 2012-01-03 21:55 UTC (permalink / raw)
To: gdb-prs
http://sourceware.org/bugzilla/show_bug.cgi?id=13473
Tom Tromey <tromey at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at redhat dot com
--- Comment #1 from Tom Tromey <tromey at redhat dot com> 2012-01-03 21:54:22 UTC ---
I agree this is a bug.
You can also see it from MI -- there is no *stopped notification.
I tested back to 7.2 and it seems to have been broken for a while.
--
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug python/13473] step N/next N does not trigger gdb.events.stop
2011-12-06 22:19 [Bug python/13473] New: step N/next N does not trigger gdb.events.stop khooyp at cs dot umd.edu
2011-12-06 22:37 ` [Bug python/13473] " khooyp at cs dot umd.edu
2012-01-03 21:55 ` tromey at redhat dot com
@ 2012-01-04 10:47 ` alves.ped at gmail dot com
2012-01-04 13:08 ` alves.ped at gmail dot com
2012-01-05 13:16 ` alves.ped at gmail dot com
4 siblings, 0 replies; 6+ messages in thread
From: alves.ped at gmail dot com @ 2012-01-04 10:47 UTC (permalink / raw)
To: gdb-prs
http://sourceware.org/bugzilla/show_bug.cgi?id=13473
Pedro Alves <alves.ped at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |alves.ped at gmail dot com
AssignedTo|unassigned at sourceware |alves.ped at gmail dot com
|dot org |
--
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug python/13473] step N/next N does not trigger gdb.events.stop
2011-12-06 22:19 [Bug python/13473] New: step N/next N does not trigger gdb.events.stop khooyp at cs dot umd.edu
` (2 preceding siblings ...)
2012-01-04 10:47 ` alves.ped at gmail dot com
@ 2012-01-04 13:08 ` alves.ped at gmail dot com
2012-01-05 13:16 ` alves.ped at gmail dot com
4 siblings, 0 replies; 6+ messages in thread
From: alves.ped at gmail dot com @ 2012-01-04 13:08 UTC (permalink / raw)
To: gdb-prs
http://sourceware.org/bugzilla/show_bug.cgi?id=13473
--- Comment #2 from Pedro Alves <alves.ped at gmail dot com> 2012-01-04 13:07:26 UTC ---
Thanks, the patch looks good.
I'll see about adding a new test case so we don't regress in the future, and
applying it to the source tree.
--
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug python/13473] step N/next N does not trigger gdb.events.stop
2011-12-06 22:19 [Bug python/13473] New: step N/next N does not trigger gdb.events.stop khooyp at cs dot umd.edu
` (3 preceding siblings ...)
2012-01-04 13:08 ` alves.ped at gmail dot com
@ 2012-01-05 13:16 ` alves.ped at gmail dot com
4 siblings, 0 replies; 6+ messages in thread
From: alves.ped at gmail dot com @ 2012-01-05 13:16 UTC (permalink / raw)
To: gdb-prs
http://sourceware.org/bugzilla/show_bug.cgi?id=13473
Pedro Alves <alves.ped at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
--- Comment #3 from Pedro Alves <alves.ped at gmail dot com> 2012-01-05 13:16:11 UTC ---
Checked in.
http://sourceware.org/ml/gdb-patches/2012-01/msg00181.html
--
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2012-01-05 13:16 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-12-06 22:19 [Bug python/13473] New: step N/next N does not trigger gdb.events.stop khooyp at cs dot umd.edu
2011-12-06 22:37 ` [Bug python/13473] " khooyp at cs dot umd.edu
2012-01-03 21:55 ` tromey at redhat dot com
2012-01-04 10:47 ` alves.ped at gmail dot com
2012-01-04 13:08 ` alves.ped at gmail dot com
2012-01-05 13:16 ` alves.ped at gmail dot com
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).