qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Trouble with GDB & Some 'Can it be done' Debugging questions
Date: Thu, 20 Jul 2006 15:17:23 -0400	[thread overview]
Message-ID: <20060720191723.GA25347@nevyn.them.org> (raw)
In-Reply-To: <BAY114-F38CDA81529C08CF233B723BD600@phx.gbl>

On Wed, Jul 19, 2006 at 08:43:57AM +0000, Steve Ellenoff wrote:
> #3) Anytime I try to dump the instruction at the current IP such as:
> (gdb) x /10i $eip
> 
> I get this - which means it's not actually reading or displaying the memory 
> properly, since those look to be what you would see if it was all 0 in 
> memory (or maybe it's all 0xff - whichever).l
> 
> 0xe05f: add    %al,(%eax)

qemu doesn't report memory errors to GDB.  It reports -1 values
instead.  This is annoying.  I think I posted a patch for it once and
never followed up when it was ignored.

It might be reading the wrong address; it might be confused due to
segmenting; it might be looking at something that would require a TLB
fault.

> #4) Can you use gdb to debug and set breakpoints on binary code you don't 
> have any source code or other file for the binary, except the binary file 
> itself? Everything I've read so far on GDB (and especially any GDB Gui 
> front end) seems to suggest it's not possible. That would really suck.

Sure you can.  It will just work.

-- 
Daniel Jacobowitz
CodeSourcery

  parent reply	other threads:[~2006-07-20 19:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-19  8:43 [Qemu-devel] Trouble with GDB & Some 'Can it be done' Debugging questions Steve Ellenoff
2006-07-20  7:11 ` Mulyadi Santosa
2006-07-27  3:11   ` Steve Ellenoff
2006-07-20 19:17 ` Daniel Jacobowitz [this message]
2006-07-20 21:04   ` Fabrice Bellard
2006-07-20 21:30     ` 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=20060720191723.GA25347@nevyn.them.org \
    --to=drow@false.org \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).