yes. If you look in a mirror, that tool is right above the eyes you
see there.
For threads, you need a "high-impedence probe" to debug. gdb is a
_very_ low-impedence probe. IE it affects the thing being tested so
drastically that it makes debugging impossible.
Most of my 'debugging' comes from stuffing critical 'trace' information
in an array (no printf's as they add synchronization that also will
change/hide bug behavior). I then print this array _after_ i reach the
condition where the bug happened. I then use my 'natural' debugger to
figure out what happened. :)
Robert Hyatt Computer and Information Sciences
[EMAIL PROTECTED] University of Alabama at Birmingham
(205) 934-2213 115A Campbell Hall, UAB Station
(205) 934-5473 FAX Birmingham, AL 35294-1170
On Thu, 3 Feb 2000, Kurt wrote:
> Hi all,
>
> are there any tools for debugging programs that use of the clone() call
> for creating kernel threads?
>
> Regards,
>
> kurt
>
> -
> Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/dmentre/smp-howto/
> To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
>
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/dmentre/smp-howto/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
