This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: glibc debugging

From: Andreas Schwab <schwab at suse dot de>
To: Chris Gniady <gniady at ecn dot purdue dot edu>
Cc: Daniel Jacobowitz <drow at mvista dot com>,libc-alpha at sources dot redhat dot com
Date: Tue, 25 Feb 2003 10:58:56 +0100
Subject: Re: glibc debugging
References: <3E54278F.9080409@ecn.purdue.edu> <je7kbv9j6k.fsf@sykes.suse.de><3E5A9832.5050804@ecn.purdue.edu><20030224221353.GA22735@nevyn.them.org><3E5A9EEE.6030800@ecn.purdue.edu>

Chris Gniady <gniady at ecn dot purdue dot 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 at suse dot 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."

References:
- glibc debugging
  - From: Chris Gniady
- Re: glibc debugging
  - From: Andreas Schwab
- Re: glibc debugging
  - From: Chris Gniady
- Re: glibc debugging
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]