public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug gdb/9796] New: SIGSEGV when restarting and running checkpoint
@ 2009-01-28 16:48 uri at 4refs dot com
  0 siblings, 0 replies; only message in thread
From: uri at 4refs dot com @ 2009-01-28 16:48 UTC (permalink / raw)
  To: gdb-prs

I encountered a SIGSEGV when restarting a checkpoint. I suspect it is because I
didn't continue past the SIGINT delivered to other processes (another bug).

Breakpoint 4, <removed> (<removed>) at top/part
(gdb) continue
  Continuing.
  <removed>

  Program received signal SIGINT, Interrupt.
  0x0000000000bd5634 in <removed (<removed>) at <removed>
(gdb) info checkpoints
  * 2 process 10971 at 0xbd5634, <removed>
    1 process 8671 at 0x7e4c28, <removed>
    0 process 7862 (main process) at 0xd099c9, <kill>
(gdb) restart 1

  Program received signal SIGINT, Interrupt.
  0x0000000000cf9be0 in lseek64 ()
  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 (lseek64) will be abandoned.
(gdb) delete checkpoint 2
  Killed process 10971
(gdb) checkpoint
  checkpoint: fork returned pid 11290.
(gdb) restart 2
  Not found: checkpoint id 2
(gdb) info checkpoints
    3 process 11290 at 0xcf9be0, <lseek64>
  * 1 process 8671 at 0xcf9be0, <lseek64>
    0 process 7862 (main process) at 0xd099c9, <kill>
(gdb) restart 3
  Switching to process 11290
  #0  0x0000000000cf9be0 in lseek64 ()
(gdb) set var <removed> = 0
(gdb) set var <removed> = 1
(gdb) set var <removed> = 1
(gdb) continue
  Continuing.
(gdb) continue
  Continuing.
Continuing.
  <removed>

  Breakpoint 4, <removed> (<removed>) at <removed>
(gdb) finish
  Run till exit from #0  <removed> (<removed>) at
  Assertion failure: <removed>
  Program received signal SIGABRT, Aborted.
  0x0000000000d099c9 in kill ()
(gdb) restart 1
  Switching to process 8671
  #0  0x0000000000cf9be0 in lseek64 ()
(gdb) delete checkpoint 3
  Killed process 11290
(gdb) restart 1
  Switching to process 8671
  #0  0x0000000000cf9be0 in lseek64 ()
(gdb) checkpoint
  checkpoint: fork returned pid 11322.
(gdb) info checkpoints
    4 process 11322 at 0xcf9be0, <lseek64>
  * 1 process 8671 at 0xcf9be0, <lseek64>
    0 process 7862 (main process) at 0xd099c9, <kill>
(gdb) restart 4
  Switching to process 11322
  #0  0x0000000000cf9be0 in lseek64 ()
(gdb) continue
  Continuing.

  Program received signal SIGSEGV, Segmentation fault.
  0x0000000000cbcf60 in __libc_start_main ()

-- 
           Summary: SIGSEGV when restarting and running checkpoint
           Product: gdb
           Version: 6.8
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: uri at 4refs dot com
                CC: gdb-prs at sourceware dot org


http://sourceware.org/bugzilla/show_bug.cgi?id=9796

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2009-01-28 16:48 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-01-28 16:48 [Bug gdb/9796] New: SIGSEGV when restarting and running checkpoint uri at 4refs dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).