From: Michael Snyder <msnyder@specifix.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: luca regini <luca.regini@gmail.com>, gdb@sourceware.org
Subject: Re: Beginner question regarding gdb symbol files
Date: Fri, 29 Feb 2008 01:10:00 -0000 [thread overview]
Message-ID: <1204227347.19253.456.camel@localhost.localdomain> (raw)
In-Reply-To: <20080228165941.GA1954@caradoc.them.org>
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...)
next prev parent reply other threads:[~2008-02-28 19:36 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 [this message]
2008-02-29 13:40 ` luca regini
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=1204227347.19253.456.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=luca.regini@gmail.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