All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: jm@poure.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] GDB help
Date: Wed, 17 Mar 2004 22:25:53 +0100	[thread overview]
Message-ID: <4058C261.4010406@bellard.org> (raw)
In-Reply-To: <200403171539.18412.jm@poure.com>

Use the executable in qemu/i386-softmmu. The symbols are stripped from 
the installed version. But be warned, debugging QEMU with gdb is not 
easy, especially if the errors are in the dynamically generated code.

Fabrice.

Jean-Michel POURE wrote:
> Dear friends,
> 
> I am trying to run the following GDB session over a Windows XP pro 
> installation disc:
> 
> root@station:/home/jmpoure/projets/qemu/winxp# gdb qemu
> GNU gdb 6.0
> Copyright 2003 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "i386-linux"...(no debugging symbols found)...
> (gdb) set args -cdrom winxp.iso -hda hd.img -boot d
> (gdb) run
> Starting program: /usr/local/bin/qemu -cdrom winxp.iso -hda hd.img -boot d
> (no debugging symbols found)...(no debugging symbols found)...(no debugging 
> symbols found)...(no debugging symbols found)...[New Thread 1077037664 (LWP 
> 3946)]
> (no debugging symbols found)...(no debugging symbols found)...(no debugging 
> symbols found)...(no debugging symbols found)...(no debugging symbols 
> found)...(no debugging symbols found)...Connected to host network interface: 
> tun0
> Detaching after fork from child process 3956.
> (no debugging symbols found)...(no debugging symbols found)...(no debugging 
> symbols found)...Serial port redirected to /dev/pts/32
> QEMU 0.5.2 monitor - type 'help' for more information
> (qemu) q
> 
> qemu was compiled from CVS. Any idea how I can get these debugging symbols?
> Then, how do I display a trace when the process detaches? Can you make a 
> detailed description for newbees? Thanks in advance.
> 
> Cheers,
> Jean-Michel
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel
> 

      reply	other threads:[~2004-03-17 21:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-17 14:39 [Qemu-devel] GDB help Jean-Michel POURE
2004-03-17 21:25 ` Fabrice Bellard [this message]

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=4058C261.4010406@bellard.org \
    --to=fabrice@bellard.org \
    --cc=jm@poure.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.