Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Sudhakar G" <list.sudhakar@gmail.com>
To: "Sudhakar G" <list.sudhakar@gmail.com>, gdb@sourceware.org
Subject: Re: debugging stripped binary/library & coredump without binary
Date: Wed, 13 Jun 2007 09:06:00 -0000	[thread overview]
Message-ID: <ce31d420706130206o5d0ab18bwd7a4581a8118f458@mail.gmail.com> (raw)
In-Reply-To: <20070612112359.GD29495@caradoc.them.org>

Thanks Daniel. But I want to know how to debug once core file is
opened without access to program file but with access only to source
code. Are there any tips?

Thanks
Sudhakar

On 6/12/07, Daniel Jacobowitz <drow@false.org> wrote:
> On Tue, Jun 12, 2007 at 04:22:43PM +0530, Sudhakar G wrote:
> > For certain reasons I want strip the symbols in my modules. But I want
> > to know how to debug the program in such case. I used to debug running
> > program at object/assembly level but only with the help of symbols
> > which help me in setting breakpoints. But with symbols stripped, I am
> > at loss as to how to debug. I know there is a command called
> > "symbol-file" in gdb which will help in loading the symbol file. Not
> > sure if it is of help. But I could not figure out how to generate
> > symbol file for a program or library though I spent some time with gcc
> > and ld man pages.
>
> You can use separate debug files, or you can just save the unstripped
> file and use that for GDB instead.
>
> > I also want to know if there is anyway in opening the coredump and
> > debugging it if the actual program is not available.
>
> gdb -c, but it does not work as well as if you give it a program.
>
> --
> Daniel Jacobowitz
> CodeSourcery
>


  reply	other threads:[~2007-06-13  9:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12 10:52 Sudhakar G
2007-06-12 11:11 ` Tavis Ormandy
2007-06-12 11:23 ` Daniel Jacobowitz
2007-06-13  9:06   ` Sudhakar G [this message]
2007-06-13  9:26     ` Andreas Schwab
2007-06-13 11: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=ce31d420706130206o5d0ab18bwd7a4581a8118f458@mail.gmail.com \
    --to=list.sudhakar@gmail.com \
    --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