This is the mail archive of the 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]

Re: Refuse following the vfork parent if not letting the child run.

On Mon, Jun 08, 2009 at 04:04:35PM +0100, Pedro Alves wrote:
> On Monday 08 June 2009 15:40:23, Pedro Alves wrote:
> > > Is this actually a fork-following error, and we've stopped execution?
> > 
> > I guess you could call it an error.  We can't satisfy the users request,
> > so we kind of stopped execution --- in reality, we're refusing to
> > continue execution, as the inferior is stopped already.
> How about?
>  (gdb) n
>  error resuming execution: can not resume the parent of a vfork in the
>  foreground if not letting the child run until it execs or exits, as
>  it would lock the terminal and hang the debug session.
>  0x00007ffff789aee4 in vfork () from /lib/
>  (gdb) 

>From the user's point of view, we might have failed to resume, or we
might have stopped a running program.  It's always helpful to offer a
suggestion.  Something like:

(gdb) n
Can not resume the parent process over vfork while holding the child
stopped.  Try "set SOMETHING" or "set SOMETHING ELSE".

Also, what about MI?

Daniel Jacobowitz

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