From: david carlton <carlton@math.stanford.edu>
To: gdb-patches@sources.redhat.com
Cc: carlton@math.stanford.edu
Subject: gdbinit.in
Date: Thu, 25 Jul 2002 17:41:00 -0000 [thread overview]
Message-ID: <15680.37429.703834.710341@jackfruit.Stanford.EDU> (raw)
When debugging GDB, if I'm looking at a function in corefile.c, it
finds the one in bfd/corefile.c rather than the one in gdb/corefile.c.
This is because, in the .gdbinit that is created in the gdb directory,
the 'dir ./../bfd' command comes later than the 'dir .' command. This
seems to me to be undesirable behavior; the accompanying patch to
gdbinit.in changes that.
I've moved both 'dir @srcdir@' and 'dir .' to the end of the dir
list. Certainly I want 'dir @srccdir@' to be towards the end. I
don't really have a strong opinion about where 'dir .' should be
- honestly, it's not entirely clear to me why it's there at all.
(@srcdir@ is . when I'm configuring this, so I don't see the
difference.)
I didn't worry about running this change through the testsuite, since
it doesn't affect GDB itself and, I assume, it doesn't affect the way
the testsuite runs.
David Carlton
carlton@math.stanford.edu
2002-07-25 david carlton <carlton@math.stanford.edu>
* gdbinit.in: Move dir @srcdir@ and dir . to the end.
Index: gdbinit.in
===================================================================
RCS file: /cvs/src/src/gdb/gdbinit.in,v
retrieving revision 1.1.1.2
diff -c -p -r1.1.1.2 gdbinit.in
*** gdbinit.in 16 Aug 1999 19:52:40 -0000 1.1.1.2
--- gdbinit.in 25 Jul 2002 23:14:58 -0000
*************** commands
*** 10,18 ****
return
end
- dir @srcdir@
- dir .
dir @srcdir@/../mmalloc
dir @srcdir@/../libiberty
dir @srcdir@/../bfd
set prompt (top-gdb)
--- 10,18 ----
return
end
dir @srcdir@/../mmalloc
dir @srcdir@/../libiberty
dir @srcdir@/../bfd
+ dir @srcdir@
+ dir .
set prompt (top-gdb)
next reply other threads:[~2002-07-26 0:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 17:41 david carlton [this message]
2002-07-26 11:17 ` gdbinit.in Jim Blandy
2002-07-26 14:30 ` gdbinit.in david carlton
2002-07-30 5:27 ` gdbinit.in Jim Blandy
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=15680.37429.703834.710341@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=gdb-patches@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