Re: Debugging sub-processes with gdb

On Wed, May 14, 2014 at 04:36:59PM +0100, Henry S. Thompson wrote: >Christopher Faylor writes: >> If you have control over the code you could have it print a pid, wait, >> and then attach to it with gdb. That works. > >Understood, will do. I should have mentioned, as an alternative approach, if y

Re: Debugging sub-processes with gdb

Christopher Faylor writes: > On Wed, May 14, 2014 at 04:10:36PM +0100, Henry S. Thompson wrote: >>I'm trying to debug a problem with xemacs that involves the child >>process forked when you execute M-x shell. >> >>None of the mechanisms in the gdb documentation for choosing to step >>into the chil

Re: Debugging sub-processes with gdb

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14.05.2014 19:25, Christopher Faylor wrote: > On Wed, May 14, 2014 at 04:10:36PM +0100, Henry S. Thompson wrote: >> I'm trying to debug a problem with xemacs that involves the child >> process forked when you execute M-x shell. >> >> None of the m

Re: Debugging sub-processes with gdb

On May 14 16:10, Henry S. Thompson wrote: > I'm trying to debug a problem with xemacs that involves the child > process forked when you execute M-x shell. > > None of the mechanisms in the gdb documentation for choosing to step > into the child process (instead of the parent) after a fork() seem t

Re: Debugging sub-processes with gdb

On Wed, May 14, 2014 at 04:10:36PM +0100, Henry S. Thompson wrote: >I'm trying to debug a problem with xemacs that involves the child >process forked when you execute M-x shell. > >None of the mechanisms in the gdb documentation for choosing to step >into the child process (instead of the parent) a

Debugging sub-processes with gdb

I'm trying to debug a problem with xemacs that involves the child process forked when you execute M-x shell. None of the mechanisms in the gdb documentation for choosing to step into the child process (instead of the parent) after a fork() seem to work for me. That is, in particular, setting foll