From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: Kevin Buettner <kevinb@redhat.com>,
jorma.laaksonen@hut.fi, gdb-gnats@sources.redhat.com,
gdb@sources.redhat.com
Subject: Re: gdb/633: fully qualified pathnames in solib_map_sections() and remote debugging
Date: Mon, 12 Aug 2002 07:37:00 -0000 [thread overview]
Message-ID: <20020812143803.GA25086@nevyn.them.org> (raw)
In-Reply-To: <3D57C611.4010403@ges.redhat.com>
On Mon, Aug 12, 2002 at 10:28:33AM -0400, Andrew Cagney wrote:
>
> >>> I think the search order needs some revision though:
> >>> - A cross debugger should not search $PATH or $LD_LIBRARY_PATH
> >
> >>
> >>I agree with this.
> >>
> >
> >>> - A cross debugger may, or may not, want to look for the unmodified
> >>> path; I suspect that we only want to look for unmodified relative
> >>> paths, not unmodified absolute ones.
> >
> >>
> >>I agree regarding absolute paths.
> >>
> >>For relative paths, I'm not convinced that it's all that useful to
> >>look at the unmodified path. (Doing so requires that you have your
> >>cwd set correctly, right?)
> >
> >
> >Yes; I think that's not too unreasonable, though. I can go either way
> >on this one; I believe it never comes up in GNU/Linux since the linker
> >fills in the full path in the link map. Not 100% sure of that,
> >however.
> >
> >
> >>> With those changes you would have to explicitly specify the path to
> >>> DSOs in a cross debugger via solib-absolute-prefix and
> >>> solib-search-path,
> >
> >>
> >>I think this would be good...
> >>
> >
> >>> and GDB would stop picking up the host libpthread.so
> >>> and making gdbserver segfault...
> >
> >>
> >>...and this too!
> >
> >
> >This leaves only the question of "how". I don't want to change the
> >behavior for a native debugger using the remote protocol; just for
> >non-native debuggers. How should I check for this? Using configury to
> >do it seems contrary to the direction gdbarch is going (i.e. a both
> >native and cross debugger in one binary).
>
> This is a target environment thing? So why not ask the target:
>
> target_getenv()
> -> qGetenv:<STRING>
> <- value
No (although I will get back to qGetenv later... :). We're discussing
the behavior of the function solib.c:solib_open. It should vary
depending on whether the current target is native or not, and I don't
know how to figure that out correctly.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-08-12 14:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020806100634.11483.qmail@sources.redhat.com>
2002-08-06 6:20 ` Daniel Jacobowitz
2002-08-09 16:12 ` Kevin Buettner
2002-08-11 20:25 ` Daniel Jacobowitz
2002-08-12 4:18 ` Jorma Laaksonen
2002-08-12 7:28 ` Andrew Cagney
2002-08-12 7:37 ` Daniel Jacobowitz [this message]
2002-08-12 8:07 ` Andrew Cagney
2002-08-12 8:48 ` Kevin Buettner
2002-08-12 8:55 ` Daniel Jacobowitz
2002-08-12 9:20 ` Kevin Buettner
2002-08-12 9:29 ` Daniel Jacobowitz
2002-08-12 9:20 ` Andrew Cagney
2002-08-12 9:31 ` Daniel Jacobowitz
2002-08-12 9:40 ` Kevin Buettner
2002-08-12 9:53 ` GDB functionalities for debugging Elf core dump Lucy Zhang
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=20020812143803.GA25086@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@ges.redhat.com \
--cc=gdb-gnats@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jorma.laaksonen@hut.fi \
--cc=kevinb@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