From: "Mandar Mitra" <mandar@isical.ac.in>
To: gdb@sourceware.org
Subject: "path" does not seem to work correctly
Date: Tue, 17 Jul 2007 10:54:00 -0000 [thread overview]
Message-ID: <64dc1fc50707162046g14063577l37bac2fa8b47fc2d@mail.gmail.com> (raw)
Hello,
I have two versions of a program (called smart):
- one compiled with -g and located in .../src/bin
- the other compiled with -O2 (without -g) and located in .../diropt/bin
The diropt/bin directory comes first on my $PATH, but in my ~/.gdbinit
file, I've re-defined "path" so that the debuggable program comes
first:
(gdb) path
Executable and object file path: .../src/bin:/bin:...:diropt/bin:.
But when I run "gdb smart", or "file smart" inside gdb, it still picks
up the optimized executable from diropt/bin.
(gdb) file smart
Reading symbols from .../diropt/bin/smart...done.
Can someone give me some hint about what I'm doing wrong?
Thanks,
Mandar.
next reply other threads:[~2007-07-17 3:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 10:54 Mandar Mitra [this message]
2007-07-17 12:43 ` Daniel Jacobowitz
2007-07-17 13:46 ` Mandar Mitra
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=64dc1fc50707162046g14063577l37bac2fa8b47fc2d@mail.gmail.com \
--to=mandar@isical.ac.in \
--cc=gdb@sourceware.org \
--cc=mandar.mitra@gmail.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