glibc debugging

Andreas Schwab schwab@suse.de
Tue Feb 25 09:58:00 GMT 2003


Chris Gniady <gniady@ecn.purdue.edu> writes:

|> Here is my dilemma. I am rather new to this and I am trying to modify read
|> and write function to generate a trace of the execution (pid and pc of the
|> caller). Can you offer any suggestion as to where I can poke in.

See sysdeps/unix/make-syscalls.sh.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."



More information about the Libc-alpha mailing list