Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Richard Tierney <mfoc73@dsl.pipex.com>
To: gdb@sources.redhat.com
Subject: How do you debug a shared library if the main app is compiled without debug?
Date: Thu, 01 Apr 2004 10:16:00 -0000	[thread overview]
Message-ID: <406BEBF5.4090600@dsl.pipex.com> (raw)

I've written a shared library (ELF/.so), with debug enabled, which is 
called from a commercial package. I don't have sources for the other 
vendor's code, and it was (I think) compiled without debug info.

Question: can I use gdb to debug my own code in this environment? If I 
set 'file' to the name of the vendor's executable then I get a message 
about there being no symbols. I've tried setting breakpoints in my own 
code, using a function name or a file and a line number, and then 
running the main app. I had assumed that the breakpoints would be set 
when my code is loaded, but this isn't happening - I get a warning about 
not being able to insert a breakpoint, and a memory access error.

Any ideas? I'm on Linux and gdb 6.0.

TIA

Rick


             reply	other threads:[~2004-04-01 10:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01 10:16 Richard Tierney [this message]
2004-04-01 14:22 ` Jim Blandy
2004-04-01 21:36   ` Richard Tierney

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=406BEBF5.4090600@dsl.pipex.com \
    --to=mfoc73@dsl.pipex.com \
    --cc=gdb@sources.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