Please forgive the naivety of this question, but my knowledge of Linux
is severely limited.
Back in the good old days of VM and CMS, it was easy to load a program,
locate it in storage, set a few CP trace traps within it, and then start
it running. How can I do the same thing in Linux?
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
Behalf Of Ray Mansell
Sent: Monday, August 21, 2006 9:23 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Tracing question
Please forgive the naivety of this question, but my knowledge of Linux
is severely limited
Ar Llu, 2006-08-21 am 10:23 -0400, ysgrifennodd Ray Mansell:
Please forgive the naivety of this question, but my knowledge of Linux
is severely limited.
Back in the good old days of VM and CMS, it was easy to load a program,
locate it in storage, set a few CP trace traps within it, and then
Hi, Ray
gdb will give you an instruction trace. Use the gdb command display/i
$pc and then use either si or ni to step instructionwise through
your program.
Richard Hitt[EMAIL PROTECTED]
Ray Mansell wrote:
Thank you both for the responses, but this isn't quite what I'm after. I
really
Thank you both for the responses, but this isn't quite what I'm after. I
really do need a CP instruction trace of a given program running in
Linux, and as far as I can tell, neither gdb nor ptrace will give me this.
Thanks again,
Ray
Alan Cox wrote:
Ar Llu, 2006-08-21 am 10:23 -0400,
Use gdb to stop the program where you are interested. Get its address. Quit
gdb. Go to the VM console:
#CP TR I R address of the routine you are interested in
(If you are in a virtual MP environment then prefix commands by #CP CPU ALL,
e.g. #CP CPU ALL TR I R ...)
Start the program.
When you
Ar Llu, 2006-08-21 am 12:28 -0400, ysgrifennodd Ray Mansell:
Thank you both for the responses, but this isn't quite what I'm after. I
really do need a CP instruction trace of a given program running in
Linux, and as far as I can tell, neither gdb nor ptrace will give me this.
They won't. Linux
Gentlemen,
Many thanks... I think I have it now. Much appreciated...
Ray
Richard Hitt wrote:
Hi, Ray
gdb will give you an instruction trace. Use the gdb command display/i
$pc and then use either si or ni to step instructionwise through
your program.
Neale Ferguson wrote:
Use gdb to stop
