Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "luca regini" <luca.regini@gmail.com>
To: gdb@sourceware.org
Cc: "Daniel Jacobowitz" <drow@false.org>
Subject: Re: Beginner question regarding gdb symbol files
Date: Fri, 29 Feb 2008 13:40:00 -0000	[thread overview]
Message-ID: <64077c280802290313j71685717q225403479ed99c63@mail.gmail.com> (raw)
In-Reply-To: <1204227347.19253.456.camel@localhost.localdomain>

The server is an openldap server. The binary comes directly from the
fedora package for it. My plugin is a custom openldap backend that is
loaded into the server using a libtool facility: lt_dlopenext.
This is the output that i get when i try run gdb slapd immediatly:

gdb slapd
(gdb) start
Breakpoint 1 at 0x14bc7: file ../../../servers/slapd/main.c, line 304.
Starting program: /opt/six/sbin/slapd
Warning:
Cannot insert breakpoint 1.
Error accessing memory address 0x14bc7: Input/output error.

This is what i got when i try to attach to the process:

 (gdb) attach 29764
Attaching to process 29764
Reading symbols from /opt/six/sbin/slapd...Reading symbols from
/opt/six/sbin/slapd.dbg...done.
Using host libthread_db library "/lib/tls/libthread_db.so.1".
done.
0x00116c68 in hex ()
(gdb)
.

If i compile openldap directly from the sources i don't have any
problem. These problems show up when i use the fedora openldap rpm
also with the debug-info package is installed.
Thanks in advance.
Luca

On Thu, Feb 28, 2008 at 8:35 PM, Michael Snyder <msnyder@specifix.com> wrote:
>
> On Thu, 2008-02-28 at 11:59 -0500, Daniel Jacobowitz wrote:
>  > On Thu, Feb 28, 2008 at 05:52:42PM +0100, luca regini wrote:
>  > > >
>  > > >  --add-gnu-debuglink is not related to this situation.  GDB should
>  > > >  automatically load symbols for your plugin when the application loads
>  > > >  it.  What doesn't work?
>  > > >
>  > >
>  > > The plug-in is loaded dynamically by the server application so it runs
>  > > in the server application address space. When i try to attach to the
>  > > server application gdb displays a message about a successeful load of
>  > > the symbols but then complains about missing source files, then i am
>  > > not able to set a breakpoint in the source of the plug-in.
>  >
>  > Sorry, this is not enough information.  We need the exact output from
>  > GDB to help you.
>
>  Yes, please attach a log of your gdb session.
>  Thanks.
>
>  You say you're using attach?
>  What happens if you launch the server under gdb?
>  What happens if you attach to the server before it dlopens the plugin?
>  (I assume you're using dlopen...)
>
>
>


  reply	other threads:[~2008-02-29 11:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21 13:47 luca regini
2008-02-21 16:53 ` Daniel Jacobowitz
2008-02-28 16:13   ` luca regini
2008-02-28 16:53     ` Daniel Jacobowitz
2008-02-28 17:00       ` luca regini
2008-02-28 17:13         ` Daniel Jacobowitz
2008-02-29  1:10           ` Michael Snyder
2008-02-29 13:40             ` luca regini [this message]
2008-02-29 18:19               ` 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=64077c280802290313j71685717q225403479ed99c63@mail.gmail.com \
    --to=luca.regini@gmail.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    /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