APM: debugging a seg fault

jeremyb at univista.com jeremyb at univista.com
Fri Sep 26 13:02:44 CDT 2003

I should have been more clear this morning.  What I meant to ask was why
sigtrace might be causing the script to race forever.

The script is 3355 lines.... 

-----Original Message-----
From: Mike South [mailto:msouth at shodor.org] 
Sent: Friday, September 26, 2003 12:54 PM
To: austin at mail.pm.org; jeremyb at univista.com
Subject: Re: APM: debugging a seg fault

hard for anyone to help without seeing the source code.  If it's not
small, then I would suggest that you cut it down to the smallest 
fraction of the program that reproduces the problem, and then post
that.  If the script is already short enough to reasonably post in
email, post it.

That "no longer shared" warning, I think, has something to do
with having a shared variable in nested subroutines.  That could
be the part of your code you want to look at if that's throwing
a warning.  But, again, it's too hard to guess without some idea
of the code.


More information about the Austin mailing list