Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: steve.kreyer@web.de
To: Daniel Jacobowitz <drow@false.org>, "Dr. Rolf Jansen" <rj@surtec.com>
Cc: gdb@sourceware.org
Subject: Re: Using dlopen and remote debugging
Date: Mon, 25 Feb 2008 14:33:00 -0000	[thread overview]
Message-ID: <1016028346@web.de> (raw)

Hi Daniel, hello Rolf,

first, thanks for your answers, but I am afraid Daniel is right. "info shared" says:
  (gdb) c
  Continuing.

  Breakpoint 1, main () at test2.c:12
  12          lib_handle = dlopen("/libtest.so", RTLD_NOW);
  (gdb) n
  13          foop = dlsym(lib_handle, "foo");
  (gdb) info shared
  No shared libraries loaded at this time.

Is there anything else I can do to debug this library using the gdb sh port?

Thanks and regards,
Steve

-----Ursprüngliche Nachricht-----
Von: "Daniel Jacobowitz" <drow@false.org>
Gesendet: 25.02.08 14:30:52
An: Steve Kreyer <steve.kreyer@web.de>
CC: gdb@sourceware.org
Betreff: Re: Using dlopen and remote debugging


On Mon, Feb 25, 2008 at 01:04:12PM +0100, Steve Kreyer wrote:
>   Breakpoint 1, main () at test2.c:12
>   12 lib_handle = dlopen("/libtest.so", RTLD_NOW);
>   (gdb) n

At this point, what does info shared say?

The SH Linux port of GDB is not well-cared-for.  I suspect it is
missing shared library support entirely.

-- 
Daniel Jacobowitz
CodeSourcery



_________________________________________________________________________
In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten! 
Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc=021114


             reply	other threads:[~2008-02-25 14:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25 14:33 steve.kreyer [this message]
2008-02-25 16:33 ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2008-02-25 19:29 Steve Kreyer
2008-02-27  1:23 ` Daniel Jacobowitz
2008-02-25 12:15 Steve Kreyer
2008-02-25 13:30 ` Dr. Rolf Jansen
2008-02-25 13:55   ` Daniel Jacobowitz
2008-02-25 14:23     ` Dr. Rolf Jansen
2008-02-25 13:32 ` 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=1016028346@web.de \
    --to=steve.kreyer@web.de \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=rj@surtec.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