This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug gdb/21328] checkpoint deadlock


https://sourceware.org/bugzilla/show_bug.cgi?id=21328

Matthias Zimmerman <matthias291999 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |matthias291999 at gmail dot com

--- Comment #1 from Matthias Zimmerman <matthias291999 at gmail dot com> ---
This is not a bug, you have a breakpoint in an area that you later call from
gdb, ie

>break exit
>p exit()
<The program being debugged was signaled while in a function called from GDB.
<GDB remains in the frame where the signal was received.
<To change this behavior use "set unwindonsignal on".
<Evaluation of the expression containing the function

Sometimes you can type `ret` until you get back to the right code, but not
always.

The stack and registers(if mangled) will not be restored(your program may go
into unintended areas) ie a while loop, in a state where it is a infinite loop.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]