Re: How to backtrace an separate stack?

2022-03-07 Thread Pedro Alves
On 2022-03-07 16:58, Tom Tromey wrote: >> "Stefan" == Stefan Hajnoczi writes: > > Stefan> I hoped that "select-frame address ADDRESS" could be used instead so > Stefan> this would work on coredumps too. Unfortunately "select-frame" only > Stefan> searches stack frames that GDB is already awar

Re: How to backtrace an separate stack?

2022-03-07 Thread Pedro Alves
On 2022-03-03 11:22, Stefan Hajnoczi wrote: > Hi, > The QEMU emulator uses coroutines with separate stacks. It can be > challenging to debug coroutines that have yielded because GDB is not > aware of them (no thread is currently executing them). > > QEMU has a GDB Python script that helps. It "cre

Re: [Qemu-devel] [PATCH] scripts/qemugdb: support coroutine backtrace in coredumps

2018-04-23 Thread Pedro Alves
he "frame" command: https://sourceware.org/ml/gdb-patches/2015-09/msg00248.html Follow the urls there for more background. To me, the important questions to answer are here: https://sourceware.org/ml/gdb-patches/2015-09/msg00658.html Unfortunately, I don't think the series moved past that point. Thanks, Pedro Alves

Re: [Qemu-devel] [PATCH] x86: Fix x86_64 'g' packet response to gdb from 32-bit mode.

2016-11-04 Thread Pedro Alves
while the infcall is running if you call a function of the "wrong" mode, etc.) I believe the MIPS 64-bit gdb port actually works that way - it always transfers 64-bit registers across the wire, and then gdb presents 32-bit registers to debugging an elf of a 32-bit ABI. I think it'

Re: [Qemu-devel] [PATCH v2 2/2] gdbstub: Fix vCont behaviour

2016-11-02 Thread Pedro Alves
es make the implementation of the stub easier. That gdb doc simplification is in master now, and live at the same url. > thanks a lot for your prompt and detailed reply! Np! Thank you too. -- Pedro Alves

Re: [Qemu-devel] [PATCH v2 2/2] gdbstub: Fix vCont behaviour

2016-10-28 Thread Pedro Alves
On 10/28/2016 02:35 PM, Claudio Imbrenda wrote: > On 27/10/16 13:40, Pedro Alves wrote: >> I'm not a qemu gdbstub expert, but FYI, seeing this reminded me to push >> to gdb's master a (getting old) gdb patch that clarifies how vCont actions >> should be interpreted

Re: [Qemu-devel] [PATCH v2 2/2] gdbstub: Fix vCont behaviour

2016-10-27 Thread Pedro Alves
27;s already live at: https://sourceware.org/gdb/current/onlinedocs/gdb/Packets.html (The "already running" case is for non-stop mode, which qemu probably doesn't support.) Thanks, Pedro Alves

Re: [Qemu-devel] [PATCH 0/4] gdbstub: improve query packet parsing, add qAttached support

2015-02-08 Thread Pedro Alves
On 02/07/2015 08:38 AM, Jan Kiszka wrote: > This addresses the review comments on the previews two patches to add > qAttached support. No longer trivial, so maybe you can pick it up, > Peter. Excellent, thanks for doing this Jan. Looks good to me. Thanks, Pedro Alves

Re: [Qemu-devel] [PATCH 1/2] Add GDB qAttached support

2015-02-04 Thread Pedro Alves
"Attached") == 0 || strncmp(p, "Attached:", 9) == 0) { Likewise other packets, if they have the same issue. (I'm not familiar with qemu's stub's internals.) Thanks, Pedro Alves

Re: [Qemu-devel] [RFA] Always consider infcall breakpoints as non-permanent.

2014-11-21 Thread Pedro Alves
work, except that some versions of QEMU (Eg: QEMU 2.0.0 for SPARC) just > + report a fatal problem (Trap 0x02 while interrupts disabled, Error > state) > + intead of reporting a SIGTRAP. QEMU should probably be fixed, but in "intead" > + the interest of compatibility with versions that behave this way, we > always > + consider bp_call_dummy breakpoint locations as non-permanent. */ > + if (loc->owner->type == bp_call_dummy) > +return 0; > + >addr = loc->address; >bpoint = gdbarch_breakpoint_from_pc (loc->gdbarch, &addr, &len); Patch is OK. Thanks Joel. Thanks, Pedro Alves