From: Daniel Jacobowitz <drow@false.org>
To: gdb guy <gdb.guy1@gmail.com>
Cc: gdb <gdb@sourceware.org>
Subject: Re: Why won't gdb stop on packed (UPX) file breakpoint at entrypoint?
Date: Wed, 26 Mar 2008 21:11:00 -0000 [thread overview]
Message-ID: <20080326210050.GA12885@caradoc.them.org> (raw)
In-Reply-To: <d662e0a00803261357j67d6e795w364ed3fc5d891f26@mail.gmail.com>
On Wed, Mar 26, 2008 at 04:57:02PM -0400, gdb guy wrote:
> (gdb) b *0xc07fd0
> Breakpoint 1 at 0xc07fd0
> (gdb) r
Known bug (well, sort of a bug, sort of a feature) in GDB. Use x/2i
0xc07fd0 and set the breakpoint at the second instruction.
> Also, just for my own benefit, and those who google after me, on GDB
> 6.3 (which I have on another older VM) what does DSO stand for when it
> says "Loading system supplied DSO at 0xc00000"?
Dynamic Shared Object. Google for vDSO.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-03-26 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 21:09 gdb guy
2008-03-26 21:11 ` Daniel Jacobowitz [this message]
2008-03-26 21:14 ` gdb guy
2008-03-26 21:18 ` Daniel Jacobowitz
2008-03-26 21:22 ` gdb guy
2008-03-26 22:36 ` 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=20080326210050.GA12885@caradoc.them.org \
--to=drow@false.org \
--cc=gdb.guy1@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