This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/12843] New: gdb failed to set a breakpoint on Windows
- From: "asmwarrior at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sun, 5 Jun 2011 01:57:23 +0000
- Subject: [Bug gdb/12843] New: gdb failed to set a breakpoint on Windows
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=12843
Summary: gdb failed to set a breakpoint on Windows
Product: gdb
Version: HEAD
Status: NEW
Severity: critical
Priority: P2
Component: gdb
AssignedTo: unassigned@sourceware.org
ReportedBy: asmwarrior@gmail.com
I build a gdb-7.3.50.20110604 cvs gdb version under MinGW and MSYS.
But when debugging, gdb failed to set a breakpoint, it seems it failed to
handle the windows style file path.
look at the log:
> break "E:/code/cb/cb_trunk/src/plugins/codecompletion/parser/parserthread.cpp:524"
No source file named E.
Breakpoint 2
("E:/code/cb/cb_trunk/src/plugins/codecompletion/parser/parserthread.cpp:524)
pending.
>>>>>>cb_gdb:
You see, "No source file named E.", this is the error message.
the gdb 20110401 cvs snapshot build works quite well on setting breakpoints.
I found that the change in linespec.c in
http://sourceware.org/ml/gdb-cvs/2011-05/msg00255.html
and
http://sourceware.org/ml/gdb-cvs/2011-05/msg00196.html
maybe cause this issue.
If I replace the linespec.c with an old version of linespec.c before May 24,
2011, then gdb build 20110604snapshot can correctly set breakpoints under
Windows.
the related discussion is
http://sourceware.org/ml/gdb/2011-06/msg00030.html
asmwarrior
ollydbg from codeblocks' forum
--
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.