From: Vladimir Prus <ghost@cs.msu.su>
To: gdb@sources.redhat.com
Subject: Filename with "./" in breakpoint command
Date: Sat, 03 Dec 2005 12:58:00 -0000 [thread overview]
Message-ID: <dms4je$qit$1@sea.gmane.org> (raw)
Hi,
I just got the following gdb session:
$ ~/build/gdb-cvs/gdb/gdb tracepoints
GNU gdb 6.4.50.20051121-cvs
(gdb) b ./tracepoints.cpp:12
No source file named ./tracepoints.cpp.
Breakpoint 1 (./tracepoints.cpp:12) pending.
(gdb) b tracepoints.cpp:12
Breakpoint 2 at 0x80483c4: file tracepoints.cpp, line 12.
(gdb) quit
$ ls tracepoints.cpp
tracepoints.cpp
It looks like leading "./" in file name confuses gdb. This "./" thing is
send by KDevelop in some cases. I'm about to fix on KDevelop side just to
make sure it works with gdb 6.4, but actually, this seems like a bug in
gdb. Say, I have two files called util.cpp -- one in current dir, and
another in some library. It's reasonable to use "./util.cpp" to refer to a
file in the current dir, no? So, is this a bug, and should I file it in the
tracker?
- Volodya
next reply other threads:[~2005-12-03 12:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-03 12:58 Vladimir Prus [this message]
2005-12-03 14:17 ` Eli Zaretskii
2005-12-03 14:22 ` Bob Rossi
2005-12-03 14:55 ` Eli Zaretskii
2005-12-03 15:01 ` Bob Rossi
2005-12-05 6:53 ` Vladimir Prus
2005-12-05 18:39 ` Eli Zaretskii
2005-12-05 18:56 ` Daniel Jacobowitz
2005-12-06 4:27 ` Eli Zaretskii
2005-12-06 4:55 ` Daniel Jacobowitz
2005-12-06 11:56 ` Bob Rossi
2005-12-06 14:01 ` Joel Brobecker
2005-12-06 14:26 ` Andrew STUBBS
2005-12-06 20:13 ` Eli Zaretskii
2005-12-06 20:11 ` Eli Zaretskii
2005-12-06 20:17 ` Daniel Jacobowitz
2005-12-06 21:02 ` Eli Zaretskii
2005-12-06 21:09 ` Daniel Jacobowitz
2005-12-06 22:32 ` Eli Zaretskii
2005-12-07 7:49 ` Vladimir Prus
2005-12-07 14:51 ` Daniel Jacobowitz
2005-12-07 16:46 ` Vladimir Prus
2005-12-08 20:53 ` Paul Gilliam
2005-12-03 14:19 ` Bob Rossi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='dms4je$qit$1@sea.gmane.org' \
--to=ghost@cs.msu.su \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox