Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: jf <jf@danglingpointers.net>
Cc: gdb@sourceware.org
Subject: Re: adding comments/labels?
Date: Wed, 29 Aug 2007 21:25:00 -0000	[thread overview]
Message-ID: <20070829212505.GA18421@caradoc.them.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0708300447550.11509@localhost.localdomain>

On Thu, Aug 30, 2007 at 04:50:40AM +0000, jf wrote:
> >
> > Not really.  I think you should do it with objcopy, instead.  Haven't
> > I suggested this to someone else recently on this list... ?
> 
> Why would I want to do it with objcopy? I'm reversing a binary and I'd
> like a label so I don't single step into the same function every time, its
> that or try to remember the address of every function I've looked at.
> 
> I'll just have to do it the hardway and cludge through the source and
> figure out where symbol resolution occurs. Thanks for the typical OSS/FS
> help ('no do it my way instead')

If you're going to be insulting when offered advice, please don't
expect to get help again.

I recommended using objcopy because objcopy supports modifying symbol
tables and GDB does not.  You can write a GDB macro to use objcopy to
add the symbol, replace the original binary, and reload it into GDB.
It'll be about five lines.  This will be about a million times easier
than trying to add a new GDB command to modify the symbol table.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-08-29 21:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-29 21:06 jf
2007-08-29 21:13 ` Daniel Jacobowitz
2007-08-29 21:18   ` jf
2007-08-29 21:25     ` Daniel Jacobowitz [this message]
2007-08-29 21:30     ` Joel Brobecker
2007-08-30 14:28 ` Baurzhan Ismagulov

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=20070829212505.GA18421@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=jf@danglingpointers.net \
    /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