Possibly unrelated seg faults (was: Re: [plt-scheme] 370/1 3m segfaults under linux)

On Oct 9, 2007, at 8:18 PM, John Clements wrote:

>
> On Oct 9, 2007, at 5:02 PM, Matthew Flatt wrote:
>
>> At Wed, 10 Oct 2007 00:43:13 +0100, John Kozak wrote:
>>> Running built-from-source versions of 370 and 371 under i386 and
>>> X86_64 strains of recentish debian linux, I'm getting segfaults:  
>>> after
>>> doing an amount of I/O (reading 1000 binary files of about 2MB  
>>> each),
>>> I get a segfault, I think in GC.  I can't confirm this, because  
>>> when I
>>> try to run mzscheme under gdb, it segfaults in startup!  Any  
>>> thoughts?
>>
>> The seg fault you see in gdb is the write barrier. Use
>>
>>  handle SIGSEGV nostop noprint
>>
>> and continue. When you get to the real problem (i.e., a seg fault  
>> that
>> isn't a write barrier), the SIGSEGV signal handler will call abort().
>>
>> Any information you can extract by running in gdb will be much
>> appreciated.
>>
>> I've fixed at least one GC bug since v371, but it's related to using
>> structs that can be applied as procedures. So, you might try the  
>> latest
>> from SVN (or using a source archive from the nightly-build page), if
>> you haven't already. My guess is that you're running into something
>> new.
>
> My students are seeing frequent seg faults, frequently on startup.   
> This is svn-oct-5, built from source on fedora 8 (not 64-bit).  One  
> of my students managed to provide a core file; unfortunately, I was  
> unable to glean anything useful by coupling it to gdb.  Here's what  
> I got:

Eli suggests that there is not yet a Fedora 8.  This detail is based  
on my memory of the machines' startup screens, and may be unreliable.

John

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2223 bytes
Desc: not available
URL: <http://lists.racket-lang.org/users/archive/attachments/20071009/c9ee1cc1/attachment.p7s>