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]

c++/2209: Unable to checkpoint after restart


>Number:         2209
>Category:       c++
>Synopsis:       Unable to checkpoint after restart
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Dec 04 16:38:02 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     uri@4refs.com
>Release:        gdb-6.5
>Organization:
>Environment:
os=Redhat Enterprise 4
arch=x86_64
>Description:
One cannot create new checkpoints after a checkpoint has been created. Looks like a deadlock occurs:

  Program received signal SIGINT, Interrupt.
  0x000000332aad16ab in __lll_mutex_lock_wait () from /lib64/tls/libc.so.6
  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 (fork) will be abandoned.
>How-To-Repeat:
1. Set 2 breakpoints and run to the first
2. "checkpoint"
3. "continue"
4. "restart 1"
5. "checkpoint"

Notice at this point that GDB hangs. By interrupting GDB you will see that it is stuck in a mutex call.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


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