From: Joakim Hove <hove@ift.uib.no>
To: gdb@sources.redhat.com
Subject: Setting breakpoint in src file located in different directory
Date: Tue, 12 Apr 2005 10:16:00 -0000 [thread overview]
Message-ID: <bjjpsx02w3b.fsf@termo1.fi.uib.no> (raw)
Hello,
I am running/debugging an executable in the path ~/RunPath
The executable in question is built from sources located in many
different directories. I (try) to set the breakpoints with the
~/.gdbinit file:
break /home/fimm/cmu/hove/libdos/src/ehist.c:694
break /home/fimm/cmu/hove/Cluster/Apps/src/Potts/Potts.c:396
This should in my opinion the breakpoints in the two files
listed. However when invoking gdb, I only get the message:
No source file named /home/fimm/cmu/hove/libdos/src/ehist.c.
No source file named /home/fimm/cmu/hove/Cluster/Apps/src/Potts/Potts.c.
I have also tried splitting it in two with:
directory /home/fimm/cmu/hove/libdos/src/
break ehist.c:694
directory /home/fimm/cmu/hove/Cluster/Apps/src/Potts/
break Potts.c:396
That succeeds for the file Potts.c (which is located in the directory
as the executable, i.e. the the executable is not located in the path
where gdb is invoked, gdb is invoked as:
%bash gdb ../exe
However the other file (ehist.c) still failed with the "No source file
named ..." message.
Any tips on how to resolve this would be greatly appreciated.
Joakim
--
Joakim Hove
hove AT ift uib no /
Tlf: +47 (55 5)8 27 90 / Stabburveien 18
Fax: +47 (55 5)8 94 40 / N-5231 Paradis
http://www.ift.uib.no/~hove/ / 55 91 28 18 / 92 68 57 04
next reply other threads:[~2005-04-12 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 10:16 Joakim Hove [this message]
2005-04-12 12:07 ` Daniel Jacobowitz
2005-04-12 12:18 ` Joakim Hove
2005-04-12 12:22 ` Daniel Jacobowitz
2005-04-12 12:59 ` Joakim Hove
2005-04-12 13:04 ` Daniel Jacobowitz
2005-04-12 13:16 ` Joakim Hove
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=bjjpsx02w3b.fsf@termo1.fi.uib.no \
--to=hove@ift.uib.no \
--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