This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/10963] New: Cannot set breakpoints on symbols containing periods in name
- From: "zonena at cs dot rpi dot edu" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: 15 Nov 2009 03:44:46 -0000
- Subject: [Bug breakpoints/10963] New: Cannot set breakpoints on symbols containing periods in name
- Reply-to: sourceware-bugzilla at sourceware dot org
When debugging an application written in amd64 assembly language (compiled with
NASM), I was unable to set breakpoints on labels local to a function which had
periods in their names.
GDB versions tested:
7.0-ubuntu on Ubuntu 9.10 amd64
6.8-debian on Ubuntu 9.04 amd64
Example source:
global printSector
printSector:
;code omitted
cmp rax, rbx
je .printLittle
;code here
.printLittle:
;code omitted
ret
When single stepping this function I was unable to set a breakpoint at the
printLittle label.
$ nm homework6 | grep printLittle
0000000000401bb1 t printSector.printLittle
(gdb) break printSector.printLittle
Can't find member of namespace, class, struct, or union named
"printSector.printLittle"
Hint: try 'printSector.printLittle<TAB> or 'printSector.printLittle<ESC-?>
(Note leading single quote.)
Make breakpoint pending on future shared library load? (y or [n])
Tab completion:
(gdb) break printSector
printSector printSector.printBig
printSector.printLittle printSector.printdirLoop
printSector.donePrinting printSector.printDirectory
printSector.printRegular printSector.printdirLoopNext
The only workaround I have found to date is to use nm to locate the address of
the target label and break at the address.
--
Summary: Cannot set breakpoints on symbols containing periods in
name
Product: gdb
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: breakpoints
AssignedTo: unassigned at sourceware dot org
ReportedBy: zonena at cs dot rpi dot edu
CC: gdb-prs at sourceware dot org
http://sourceware.org/bugzilla/show_bug.cgi?id=10963
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.