Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: nak26 <nak26@drexel.edu>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: pthread_db innitializing error
Date: Thu, 26 Jun 2003 14:44:00 -0000	[thread overview]
Message-ID: <20030626144425.GA19550@nevyn.them.org> (raw)
In-Reply-To: <3EFAF51F@webmail.drexel.edu>

On Thu, Jun 26, 2003 at 10:34:37AM -0400, nak26 wrote:
> >
> >Is GDB on the host finding the _host's_ libpthread, or the _target's_
> >libpthread copied to the host?
> >
> >It must be the latter if you want it to work.
> >
> 
> It finds the latter, but errors when trying to load it automatically.
> I guess the warning that comes out after the connection is made points to
> why this is happening.
> 
> ----------------------------------
> GDB console's output
> ----------------------------------
> (gdb) b main
> Breakpoint 1 at 0x82a2cc2: file ../cp/tlpcp.cxx, line 332.
> (gdb) target remote 192.168.139.14:7000
> Remote debugging using 192.168.139.14:7000
> 0x40001390 in ?? ()
> warning: Unable to find dynamic linker breakpoint function.
> GDB will be unable to debug shared library initializers
> and track explicitly loaded dynamic code.
> (gdb) c
> Continuing.
> Error while mapping shared library sections:
> /lib/libnsl.so.1: No such file or directory.
> Error while mapping shared library sections:
> /lib/librt.so.1: No such file or directory.
> Error while mapping shared library sections:
> /lib/libpthread.so.0: No such file or directory.
> Error while mapping shared library sections:
> /opt/intel/mkl/lib/32/libmkl_p4.so: No such file or directory.
> Error while mapping shared library sections:
> /opt/intel/mkl/lib/32/libguide.so: No such file or directory.
> Error while mapping shared library sections:
> /usr/lib/libstdc++.so.5: No such file or directory.
> Error while mapping shared library sections:
> /lib/libm.so.6: No such file or directory.
> Error while mapping shared library sections:
> /lib/libgcc_s.so.1: No such file or directory.
> Error while mapping shared library sections:
> /lib/libc.so.6: No such file or directory.
> Error while mapping shared library sections:
> /lib/ld-linux.so.2: No such file or directory.
> --------------------------------------------
> GDBSERVER's console output
> --------------------------------------------
> Process tlpSim created; pid = 2884
> Remote debugging from host 192.168.66.59
> gdb: Unable to set global thread event mask: generic error
> gdb: Unable to set global thread event mask: generic error
> gdb: Unable to set global thread event mask: generic error
> gdb: Unable to set global thread event mask: generic error
> gdb: Unable to set global thread event mask: generic error
> gdb: Unable to set global thread event mask: generic error
> gdb: Unable to set global thread event mask: generic error
> gdb: Unable to set global thread event mask: generic error
> 
> Is this a (_remote_) linker issue or gdbserver issue or (_local_)
> gdb issue?
> Furthermore, does gdb load the shared libraries from the remote
> machine over the network or they need to reside locally?

They need to reside locally, and this is a local gdb issue.

From the error message above, GDB is not finding the library -
otherwise you wouldn't get "No such file or directory".  Please take
another look at the documentation for solib-absolute-prefix.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-06-26 14:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-26 14:34 nak26
2003-06-26 14:44 ` Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-25 18:31 nak26
2003-06-26  4:58 ` Daniel Jacobowitz
2003-06-25 17:01 nak26
2003-06-25 18:30 ` Daniel Jacobowitz

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=20030626144425.GA19550@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=nak26@drexel.edu \
    /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