From: Michael Snyder <msnyder@redhat.com>
To: Kris Warkentin <kewarken@qnx.com>
Cc: Kevin Buettner <kevinb@redhat.com>,
Daniel Jacobowitz <drow@mvista.com>,
"Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: Re: Why does solib_open do what it does?
Date: Wed, 18 Jun 2003 20:10:00 -0000 [thread overview]
Message-ID: <3EF0C723.3000109@redhat.com> (raw)
In-Reply-To: <019f01c335cd$0a119c80$0202040a@catdog>
Kris Warkentin wrote:
>msnyder:
>>Kris Warkentin wrote:
>>I rather think that $PATH and $LD_LIBRARY_PATH should be native-only.
>>But come to think of it, do remote targets even have environment
>>variables?
>
>>And if so -- do they inherit them from gdb / the host? If there's a
>>gdbserver-type situation, and if the server is able to provide the true
>>environment variables from the target, then yes, we should use these.
>>But I don't recall any gdbserver ever offering that functionality.
>
> Our pdebug remote protocol allows us to 'set qnxinheritenv true/false'.
> This determines whether gdb will send it's environment to the target or
> whether the target will inherit from the pdebug server.
Cool, and I presume you can then read them back.
In that case, (assuming the child inherits from the target side server),
wouldn't you want LD_LIBRARY_PATH to be searched? If the linker-loader
picks up libc from one place, but gdb picks it up from someplace else,
you're hosed.
next prev parent reply other threads:[~2003-06-18 20:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 19:01 Kris Warkentin
2003-06-17 19:13 ` Daniel Jacobowitz
2003-06-17 19:14 ` Kris Warkentin
2003-06-17 19:37 ` Elena Zannoni
2003-06-17 19:47 ` Kris Warkentin
2003-06-17 20:01 ` Kevin Buettner
2003-06-17 20:15 ` Kris Warkentin
2003-06-17 20:24 ` Kevin Buettner
2003-06-18 0:14 ` Michael Snyder
2003-06-18 1:43 ` Kris Warkentin
2003-06-18 5:33 ` Kevin Buettner
2003-06-18 12:11 ` Kris Warkentin
2003-06-18 15:07 ` Kris Warkentin
2003-06-18 18:52 ` Michael Snyder
2003-06-18 19:09 ` Kris Warkentin
2003-06-18 19:20 ` Andrew Cagney
2003-06-18 20:10 ` Michael Snyder [this message]
2003-06-18 20:17 ` Kris Warkentin
2003-06-18 19:14 ` Daniel Jacobowitz
2003-06-18 18:45 ` Michael Snyder
2003-06-18 18:41 ` Michael Snyder
2003-06-18 19:16 ` Daniel Jacobowitz
2003-06-18 20:11 ` Michael Snyder
2003-06-18 20:19 ` Kris Warkentin
2003-06-18 20:27 ` Daniel Jacobowitz
2003-06-18 20:51 ` Michael Snyder
2003-06-19 12:24 ` Kris Warkentin
2003-06-19 23:33 ` Kevin Buettner
2003-06-20 0:02 ` Kevin Buettner
2003-06-20 12:28 ` Kris Warkentin
2003-06-20 12:43 ` Kevin Buettner
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=3EF0C723.3000109@redhat.com \
--to=msnyder@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@redhat.com \
--cc=kewarken@qnx.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