[Bug c++/9311] Checkpointing SIGINT on restart

[Bug c++/9311] Checkpointing SIGINT on restart

[pedro at codesourcery dot com]

------- Additional Comments From pedro at codesourcery dot com  2009-01-20 00:27 -------
Could you please check if this happens with current mainline?

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |WAITING


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

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

[Bug c++/9311] Checkpointing SIGINT on restart

[uri at 4refs dot com]

------- Additional Comments From uri at 4refs dot com  2009-01-20 18:56 -------
I was able to reproduce it using 6.8.50.20090119. Here's the GDB log:

  Breakpoint 2, <removed> (<removed>) at <removed>
(gdb) checkpoint
  checkpoint: fork returned pid 22207.
(gdb) continue
  Continuing.
  <removed>

  Program received signal SIGINT, Interrupt.
  0x000000000042f362 in <removed> (<removed>) at <removed>
(gdb) restart 1

  Program received signal SIGINT, Interrupt.
  0x0000000000cf9b00 in lseek ()
  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 (lseek) will be abandoned.
(gdb) info checkpoints
  * 1 process 22207 at 0xcf9b00, <lseek>
    0 process 22127 (main process) at 0x42f362, file <removed>


-- 


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

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

[Bug c++/9311] Checkpointing SIGINT on restart

[pedro at codesourcery dot com]

------- Additional Comments From pedro at codesourcery dot com  2009-01-21 18:35 -------
Ok, it wasn't clear from you original report, but, IIUC, this happens
when the current "checkpoint/fork" gets a SIGINT (due to ctrl-c, I assume),
and then, you restart another checkpoint.

Keeping in mind that checkpoints are processes, it sounds like
the ctrl-c SIGINT, being delivered to the whole group, and then the
restarted checkpoint gets the signal delivered the first time it
is resumed --- restarting a checkpoint calls lseek in it, so that
would be when.

Am I understanding correctly, or can this also happen
in other circumstances?


-- 


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

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

[Bug c++/9311] Checkpointing SIGINT on restart

[uri at 4refs dot com]

------- Additional Comments From uri at 4refs dot com  2009-01-21 19:34 -------
I think your understanding is correct. I don't know of any other circumstances.

-- 


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

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