All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Matt Davis <mattdavis9@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: 64-bit Qemu and remote GDB to Kernel Error
Date: Mon, 04 Oct 2010 11:00:07 +0200	[thread overview]
Message-ID: <4CA99797.7000402@siemens.com> (raw)
In-Reply-To: <AANLkTikSea9Z=0MiPSTOb=Sz+0QszJQR7oF0k=3DoY4V@mail.gmail.com>

Am 04.10.2010 04:47, Matt Davis wrote:
> Hello,
> I am trying to debug a 32-bit linux kernel with gdb and qemu.  My qemu
> runs the 64-bit kernel as:
> user@host> qemu -kernel vmlinuz -S -s  (not using kvm).  If I try with
> kvm the breakpoint does not even seem to get tripped.

Which qemu version is affected by this issue?

> 
> And then I fire up gdb on my 64-bit machine (the same one running
> qemu).  And I set my "target remote :1234" and set a breakpoint.
> Anyways, I seem to catch my breakpoint, but when it should be tripping
> I get the following error :
> Remote 'g' packet reply is too long: <data>
> 
> I have done similar stuff fine on a 32bit machine running both 32-bit
> qemu and a 32-bit kernel.  I have also googled, and this seems to not
> be uncommon (circa 2008).  But I have not seen anything recently
> regarding this.  Should it be working now?  If not is there a better
> solution?  I tried, on my 64bit machine, to run a 32-bit kernel in
> qemu, but my breakpoints were still not tripping in gdb.  Yes, the
> kernel did have debugging flags built in.  I also forced the gdb
> architecture to use "set arch i386:x86-64" not much difference if I
> recall.
> 
> The following thread had similar issues when trying to set a break in
> 64 bit land, but not mention of the error I reported above.  These
> possibly cold be related:
> http://lists.gnu.org/archive/html/qemu-devel/2008-05/msg00287.html

Please also see this thread
http://thread.gmane.org/gmane.comp.emulators.qemu/80327. Did you follow
the procedure I suggested? I cannot derive this from your description.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2010-10-04  9:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04  2:47 [Qemu-devel] 64-bit Qemu and remote GDB to Kernel Error Matt Davis
2010-10-04  9:00 ` Jan Kiszka [this message]
2010-10-04 21:32   ` [Qemu-devel] " Matt Davis
2010-10-05  7:36     ` Jan Kiszka

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=4CA99797.7000402@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=mattdavis9@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.