This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/13692] New: strange behavior for pending "digit"breakpoints
- From: "tromey at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 14 Feb 2012 21:37:12 +0000
- Subject: [Bug breakpoints/13692] New: strange behavior for pending "digit"breakpoints
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=13692
Bug #: 13692
Summary: strange behavior for pending "digit" breakpoints
Product: gdb
Version: 7.4
Status: NEW
Severity: normal
Priority: P2
Component: breakpoints
AssignedTo: unassigned@sourceware.org
ReportedBy: tromey@redhat.com
Classification: Unclassified
Created attachment 6213
--> http://sourceware.org/bugzilla/attachment.cgi?id=6213
patch with at test case
A pending all-digit breakpoint shows up strangely in "info b":
(gdb) b 99999
No line 99999 in the current file.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (99999) pending.
(gdb) info b
Num Type Disp Enb Address What
1 breakpoint keep y <PENDING> 99999
The canonical form here really ought to include the current file's
name, like "linespec.cc:99999".
The difficulty is that pending breakpoints are handled via an exception,
and there is no facility to pass the canonical form along.
--
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.