Segmentation faults

Tue Sep 4 09:25:00 GMT 2001

What does the client code look like? It sounds like you're calling execve
directly from the gcj process, not from a forked child? What platform are
you on?
This sounds a bit like other threads are not getting killed before an
execve? As far as I can tell, glibc on Linux at least attempts to do this
right.
Hans
> -----Original Message-----
> From: Andrew Haley [ mailto:aph@cambridge.redhat.com ]
> Sent: Tuesday, September 04, 2001 2:10 PM
> To: Bryan Ha
> Cc: tromey@redhat.com; java@gcc.gnu.org
> Subject: Re: Segmentation faults
>>> =?iso-8859-1?Q?Bryan=5FHa?= writes:
> > Tom,
> > 
> > I am using the char*[] I got out from the jstringarray
> > using the procedure you showed me last time. I have
> > printed out the arguments and it seems okay.
> > 
> > Anyway, if this has been done before, I have done
> > something wrong. I will check that again.
>> Lotsa times. Look at name-finder.cc and name-finder.h for a simple
> example of execve used with gcj.
>> My guess is that you're having some sort of conflict with the garbage
> collector.
>> Andrew.
>