From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sources.redhat.com
Cc: Andrew STUBBS <andrew.stubbs@st.com>
Subject: Re: [PATCH] Use search path for scripts
Date: Fri, 25 Nov 2005 22:33:00 -0000 [thread overview]
Message-ID: <u1x14zdnh.fsf@gnu.org> (raw)
In-Reply-To: <20051125181735.GF736@nevyn.them.org> (message from Daniel Jacobowitz on Fri, 25 Nov 2005 13:17:35 -0500)
> Date: Fri, 25 Nov 2005 13:17:35 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sources.redhat.com
>
> Most users don't ever have to add a source path. If you're using a
> modern compiler, and debugging something built locally, and not using
> certain kinds of include path constructs (which is unambiguously an
> open, and recently discussed, bug in GDB) then GDB will Just Find
> Things.
Would it be reasonable to make GDB look for scripts in the source file
directories recorded in the debug info? Assuming you accept the
argument that scripts are usually in the source tree, that sounds
plausible, no?
next prev parent reply other threads:[~2005-11-25 20:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 19:36 Andrew STUBBS
2005-11-17 0:04 ` Eli Zaretskii
2005-11-17 12:41 ` Andrew STUBBS
2005-11-17 19:42 ` Eli Zaretskii
2005-11-18 13:23 ` Andrew STUBBS
2005-11-18 14:53 ` Eli Zaretskii
2005-11-18 15:54 ` Andrew STUBBS
2005-11-25 18:02 ` Andrew STUBBS
2005-11-25 18:12 ` Daniel Jacobowitz
2005-11-25 18:33 ` Andrew STUBBS
2005-11-25 18:39 ` Daniel Jacobowitz
2005-11-25 20:12 ` Andrew STUBBS
2005-11-25 21:26 ` Daniel Jacobowitz
2005-11-25 22:33 ` Eli Zaretskii [this message]
2005-11-28 19:34 ` Andrew STUBBS
2005-11-25 21:56 ` Eli Zaretskii
2005-11-25 21:43 ` Eli Zaretskii
2006-01-12 0:09 ` Andrew STUBBS
2006-01-22 20:40 ` Daniel Jacobowitz
2006-01-23 16:29 ` Andrew STUBBS
2006-01-23 17:41 ` Andrew STUBBS
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=u1x14zdnh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.stubbs@st.com \
--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