All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yolkfull Chow <yzhou@redhat.com>
To: "Saksena, Abhishek" <abhishek.saksena@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: GDB Debugging
Date: Sun, 25 Oct 2009 00:44:25 +0800	[thread overview]
Message-ID: <20091024164424.GA4196@aFu.nay.redhat.com> (raw)
In-Reply-To: <4158487B9DEE0647BA23911D1C22795712E24F98DA@orsmsx501.amr.corp.intel.com>

On Fri, Oct 23, 2009 at 09:19:40AM -0700, Saksena, Abhishek wrote:
> 
> Hi Guys,
> 
> Any help will be appreciated on following issue. I have been struggling on this for quite some time...
> 
> 
> -Abhishek
> 
> 
> 
> -----Original Message-----
> From: Saksena, Abhishek 
> Sent: Tuesday, October 20, 2009 11:49 AM
> To: 'Jan Kiszka'
> Cc: kvm@vger.kernel.org
> Subject: GDB + KVM Debug
> 
> I have now tried using both
> 
> 
> Set arch i8086 and 
> Set arch i386:x86-64:intel 

Try 'set architecture i386:x86-64'.

> 
> But still see the same issue. Do I need to apply any patch?
> 
> 
> Abhishek
> 
> -----Original Message-----
> From: Jan Kiszka [mailto:jan.kiszka@siemens.com] 
> Sent: Thursday, September 17, 2009 1:36 AM
> To: Saksena, Abhishek
> Cc: kvm@vger.kernel.org
> Subject: Re: GDB + KVM Debug
> 
> Saksena, Abhishek wrote:
> > I am using KVM-88. However I can't get gdb still working. I stared qemu with -s -S option and when I try to connect gdb to it I get following error:-
> > 
> > (gdb) target remote lochost:1234
> > lochost: unknown host
> > lochost:1234: No such file or directory.
> > (gdb) target remote locahost:1234
> > locahost: unknown host
> > locahost:1234: No such file or directory.
> > (gdb) target remote localhost:1234
> > Remote debugging using localhost:1234
> > [New Thread 1]
> > Remote 'g' packet reply is too long: 0000000000000000000000000000000000000000000000002306000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000f0ff0000000000000230020000f00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007f03000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
> 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
> > (gdb)
> > 
> 
> Try 'set arch <target-architecture>' before connecting. This is required
> if you didn't load the corresponding target image into gdb.
> 
> Jan
> 
> -- 
> Siemens AG, Corporate Technology, CT SE 2
> Corporate Competence Center Embedded Linux
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-10-24 16:44 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 10:04 vhost-net todo list Michael S. Tsirkin
2009-09-16 14:52 ` Arnd Bergmann
2009-09-16 14:58   ` Michael S. Tsirkin
2009-09-16 14:58   ` Michael S. Tsirkin
2009-09-16 15:08     ` Arnd Bergmann
2009-09-16 15:19       ` Michael S. Tsirkin
2009-09-16 15:19       ` Michael S. Tsirkin
2009-09-16 15:27         ` Arnd Bergmann
2009-09-16 15:46           ` GDB + KVM Debug Saksena, Abhishek
2009-09-16 16:02             ` Jan Kiszka
2009-09-16 16:24               ` Saksena, Abhishek
2009-09-16 16:37                 ` Jan Kiszka
2009-09-16 17:15                   ` Avi Kivity
2009-09-16 17:56                     ` Jan Kiszka
2009-09-16 18:26                       ` Avi Kivity
2009-09-16 18:49                   ` Saksena, Abhishek
2009-09-17  8:35                     ` Jan Kiszka
2009-10-20 18:48                       ` Saksena, Abhishek
2009-10-23 17:01                         ` Jan Kiszka
2009-10-23 16:19                       ` GDB Debugging Saksena, Abhishek
2009-10-24 16:44                         ` Yolkfull Chow [this message]
2009-09-16 16:45           ` vhost-net todo list Michael S. Tsirkin
2009-09-16 16:45           ` Michael S. Tsirkin
2009-09-17 11:30             ` Arnd Bergmann
2009-09-17 11:30             ` Arnd Bergmann
2009-09-17 11:47               ` Michael S. Tsirkin
2009-09-17 12:14                 ` Arnd Bergmann
2009-09-17 12:14                 ` Arnd Bergmann
2009-09-17 12:25                   ` Michael S. Tsirkin
2009-09-17 12:25                   ` Michael S. Tsirkin
2009-09-17 15:08                     ` Arnd Bergmann
2009-09-17 15:08                     ` Arnd Bergmann
2009-09-17 11:47               ` Michael S. Tsirkin
2009-09-16 17:13           ` Avi Kivity
2009-09-16 17:13           ` Avi Kivity
2009-09-16 15:27         ` Arnd Bergmann
2009-09-16 15:08     ` Arnd Bergmann
2009-09-16 15:01   ` Michael S. Tsirkin
2009-09-16 15:01   ` Michael S. Tsirkin
2009-09-16 14:52 ` Arnd Bergmann

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=20091024164424.GA4196@aFu.nay.redhat.com \
    --to=yzhou@redhat.com \
    --cc=abhishek.saksena@intel.com \
    --cc=kvm@vger.kernel.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.