[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/16284 running function in stoped gdb ...
The following reply was made to PR kern/16284; it has been noted by GNATS.
From: David Laight <david%l8s.co.uk@localhost>
Subject: Re: kern/16284 running function in stoped gdb ...
Date: Sun, 3 Jan 2010 21:07:54 +0000
This still happens, errno is unchanged and the 'ret' value
from select() seems to be undefined.
ktrace shows a 'RET syscall 0' for the return from select
errno is unchanged (unless set in the called function).
gdb has to do some horrid stuff in order to call a process
function - and even the 'success' result is lost.
Sometimes, but not always, I also see almost 2 seconds delay before
the output from the called function - not sure where that delay comes from.
(A 2nd ^C gives a "Corrupt Obj_Entry pointer in GOT" error.)
Anyone know the ptrace interface well enough to know what gdb is
trying to do ?
David Laight: david%l8s.co.uk@localhost
Main Index |
Thread Index |