From: Daniel Jacobowitz <drow@mvista.com>
To: Robert Schweikert <Robert.Schweikert@hks.com>
Cc: kevinb@redhat.com, gdb@sources.redhat.com
Subject: Re: Shared library problems
Date: Tue, 24 Sep 2002 08:30:00 -0000 [thread overview]
Message-ID: <20020924153048.GA13807@nevyn.them.org> (raw)
In-Reply-To: <3D90847F.3864E508@hks.com>
On Tue, Sep 24, 2002 at 11:27:59AM -0400, Robert Schweikert wrote:
> Daniel Jacobowitz wrote:
>
> > On Tue, Sep 24, 2002 at 11:21:13AM -0400, Robert Schweikert wrote:
> > > Daniel Jacobowitz wrote:
> > >
> > > > On Mon, Sep 23, 2002 at 09:01:59PM -0400, Robert Schweikert wrote:
> > > > > Kevin,
> > > > >
> > > > > > Which version of gdb are you using? Which host and target?
> > > > >
> > > > > Acording to the package id I am using 5.0-148. gdb produces the following
> > > > > output.
> > > > >
> > > > > -> gdb -v
> > > > > GNU gdb 20010316
> > > > >
> > > > > This is on Linux running on Intel IA32.
> > > >
> > > > Try a more recent version:
> > > > http://sources.redhat.com/gdb
> > > >
> > > > That one's pretty old. And we have no idea what your distributor did
> > > > with the 148 revisions of it...
> > >
> > > Daniel,
> > >
> > > I downloaded the latest source and built the 5.2.1 version but I end up with
> > > the same symptom.
> > >
> > > i.e. start gdb within the proper environment and try to run the app from there
> > > I end up with the problem that the app cannot find the shared libraries.
> > > Displaying LD_LIBRARY_PATH in gdb (show env LD_LIBRARY_PATH) shows that the
> > > path to the library that cannot be found is on the LD_LIBRARY_PATH.
> >
> > I assume I know what's going on, then. Do your shell startup files
> > include a different setting of LD_LIBRARY_PATH?
>
> Yes, they certainly do.
>
> >
> >
> > Right now GDB spawns a copy of your shell to start the debugged
> > application. We've been getting a lot of bad noises about this
> > behavior lately, so it may be reaching the end of its life span...
>
> Is there a work around?
I can't really think of one. Maybe include the necessary
LD_LIBRARY_PATH in your shell startup files - or better yet, don't
change LD_LIBRARY_PATH in said files if it is already set. These may
or may not be feasible in your environment.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-09-24 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 18:02 Robert Schweikert
2002-09-23 18:29 ` Daniel Jacobowitz
2002-09-24 8:21 ` Robert Schweikert
2002-09-24 8:25 ` Daniel Jacobowitz
2002-09-24 8:27 ` Robert Schweikert
2002-09-24 8:30 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-19 5:35 Robert Schweikert
2002-09-19 10:46 ` 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=20020924153048.GA13807@nevyn.them.org \
--to=drow@mvista.com \
--cc=Robert.Schweikert@hks.com \
--cc=gdb@sources.redhat.com \
--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