This is the mail archive of the
mailing list for the GDB project.
Re: [patch] Fix Linux attach to signalled/stopped processes
- From: Daniel Jacobowitz <drow at false dot org>
- To: Roland McGrath <roland at redhat dot com>
- Cc: Jan Kratochvil <jan dot kratochvil at redhat dot com>, Doug Evans <dje at google dot com>, GDB Patches <gdb-patches at sourceware dot org>, mark dot kettenis at xs4all dot nl
- Date: Thu, 10 Apr 2008 11:15:45 -0400
- Subject: Re: [patch] Fix Linux attach to signalled/stopped processes
- References: <firstname.lastname@example.org> <20080401223012.GA14076@host0.dyn.jankratochvil.net> <20080401224936.5F0EC26F8DC@magilla.localdomain>
On Tue, Apr 01, 2008 at 03:49:36PM -0700, Roland McGrath wrote:
> I'm not sure if there was any question for me about kernel behavior in there.
> As a gdb user, I have long been annoyed by the behavior on attaching to a
> stopped process. What I want is for attach to complete immediately and let
> me examine the process. If I then "cont", the process should go back to
> what it was doing--sitting in job control stop. Then fg or otherwise
> sending SIGCONT will wake it up normally, and gdb should stop and tell me
> about the SIGCONT like normal.
How could GDB put an attached process back into job control stop?