On Tue, Jul 08, 2003 at 06:50:53PM +0900, Richard Zidlicky wrote:
> On Mon, Jul 07, 2003 at 08:07:21AM +0900, Nigel Gilbert wrote:
> > Could your segmentation fault be due to  the same problem as in the  
> > following?
> 
> it could be the same or related, but so far all symptoms
> described seem much to random to be debugged.
> Does anyone have a truly repeatable testcase? 
> 
> BTW does ruby have an option to dump cure instead of 
> catching the segfault?

I did the following:
 * comment the following lines in signal.c (around line 736)
   #ifdef SIGSEGV
           install_sighandler(SIGSEGV, sigsegv);
   #endif
 * compile and rename the binary to gruby, then put it in my path

This way I can get core dumps when debugging rjni.

-- 
 _           _                             
| |__   __ _| |_ ___ _ __ ___   __ _ _ __  
| '_ \ / _` | __/ __| '_ ` _ \ / _` | '_ \ 
| |_) | (_| | |_\__ \ | | | | | (_| | | | |
|_.__/ \__,_|\__|___/_| |_| |_|\__,_|_| |_|
	Running Debian GNU/Linux Sid (unstable)
batsman dot geo at yahoo dot com

<dark> Turns out that grep returns error code 1 when there are no matches.
       I KNEW that.  Why did it take me half an hour?
	-- Seen on #Debian