As mentioned by Horst, hbreak is needed.
If you are getting "Remote 'g' packet reply is too long", see:
https://sourceware.org/bugzilla/show_bug.cgi?id=13984
** Bug watch added: Sourceware.org Bugzilla #13984
http://sourceware.org/bugzilla/show_bug.cgi?id=13984
--
You received this bug notif
More details:
- It works if I use hbreak (GDB hardware-assisted breakpoints) instead of
break for the very first breakpoint.
- After this first breakpoint, normal "break" breakpoints work fine, too.
- Accoording to
http://chemnitzer.linux-tage.de/2012/vortraege/folien/1061-VirtualDebugging.pdf
status confirmed
** Changed in: qemu-kvm (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901944
Title:
gdbserver inside qemu does not stop on breakpoints
I'm seeing the very same problem, please reopen.
Ubuntu 12.10 amd64 (Linux 3.5.0-25-generic x86_64), qemu-kvm
1.2.0+noroms-0ubuntu2.12.10.3. Guest is an i386 eCos test kernel (I can attach
it if necessary; I guess you can use anything bootable here), started either via
qemu-system-i386 -kernel
[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9019
This config lets me debug the kernel. However, I can not start debugging
with qemu's -S option. With -S, qemu waits for a gdb connection to start
the VM but gdb can't connect to the default port (:1234). Connection
times out.
If I start with -s, then everything is good.
** Attachment added: "kern
Do you mind posting the new, working, config? There may (likely will)
be too much noise in the diff, but it's worth looking for clues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901944
Title:
gd
I reconfigured the kernel from the default configuration with the
debugging symbols and it now seems to be working okay. There is
something in the config I previously posted that makes things weird. The
question is how can we track it down?
--
You received this bug notification because you are a
** Attachment added: "kernel config file for 2.6.38-10-server"
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/901944/+attachment/2625885/+files/.config
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Thanks - please do attach your .config, and I'll try to reproduce.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901944
Title:
gdbserver inside qemu does not stop on breakpoints
To manage notificat
Guest is a 2.6.38-10-server x86_64 kernel with ubuntu patches applied
(configured to have some set of modules built-in + debugging symbols +
non-preemptive + HZ=100). I can provide the config file if necessary.
Root fs contains a minimal 10.04 server.
Here is how I launch the VM:
$ qemu-system-x86
Thanks for reporting this bug.
Could you show us exactly how to reproduce your failure and what to look
for? I see you are on oneiric. We have somewhat recently,
successfully, used gdb remotely on oneiric, but it was with very early
boot which may affect this. Could you tell us which release+ke
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901944
Title:
gdbserver inside qemu does not stop on breakpoints
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source
13 matches
Mail list logo
