Re^4: How to find perl line after segfault.

Hi QM,

It looks like the printouts are produced by CallTrace, So I'd have to modify CallTrace to use 'tee', is that what you are suggesting?

As it's being called with -d, I don't imagine tee in the child program or the parent program will make much difference.

At the moment CallTrace writes to STDERR, but it could be tee'd to another file too, do you think?

Regards

Steve.

Comment on Re^4: How to find perl line after segfault.

Replies are listed 'Best First'.
Re^5: How to find perl line after segfault. by QM (Parson) on Feb 16, 2015 at 09:18 UTC
Whatever is dumping to the screen should be teed to a file. You may have to redirect STDERR to do so (which is shell-dependent, I always look at Unix Power Tools: Common Standard I/O Redirections). This may involve changing the command line call. Or CallTrace may allow you to log directly to a file. (I know nothing about CallTrace. It's a generic-enough term that it's hard for me to decide which software you are referring to.) Another choice is to use script to log the entire session. This starts a new shell, where you can then run your commands. -QM -- Quantum Mechanics: The dreams stuff is made of	[reply]

Replies are listed 'Best First'.

Re^5: How to find perl line after segfault.
by QM (Parson) on Feb 16, 2015 at 09:18 UTC

Unix Power Tools: Common Standard I/O Redirections

This may involve changing the command line call. Or CallTrace may allow you to log directly to a file. (I know nothing about CallTrace. It's a generic-enough term that it's hard for me to decide which software you are referring to.)

Another choice is to use script to log the entire session. This starts a new shell, where you can then run your commands.

-QM
--
Quantum Mechanics: The dreams stuff is made of

[reply]