comment on

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

In reply to Re^5: How to find perl line after segfault. by QM
in thread How to find perl line after segfault. by Steve_BZ

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Your skill will accomplish what the force of many cannot
	PerlMonks