Re: GDB: "warning: Can't wait for pid ???: No child processes" (was: GNU accepted as a mentoring organization in GSOC 2014)

[Yue Lu]

Hi!

On Tue, Apr 8, 2014 at 11:26 PM, Zhang Cong <congzhang@mathphoenix.com> wrote:

 Why, I can't understand ? the gdb server be the debugged program's parent, right?

 And gdb just interactive with gdb server and gdbserver interactive with the debugged program, right?

Yes, if you use the gdbserver to start the debugged, the gdbserver is its parent. If you just attach to a exist one, the gdbserver will not be the parent like native gdb does on Hurd.

 

 If gdbserver run on another machine, when I remote debug, that's impossible to make the gdb to be the parent of debugged program, right?

 Why shoud gdb server need to re-parent process? 

 

If native gdb works, the gdb server way should work, and now the native way support continue, so the gdb server should ,too. 

Or, please told me why.

The reason is that the native _GDB_ doesn't work either on Hurd. So as gdbserver. You can try to attach to a exist process by GDB, you will get that warnning. In detail, there is no distinct difference between the implementation of GDB and gdbserver. They are the same.

--

Yue Lu (陆岳)