[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gdnc segfaulting in sarray.h, internal to gcc-3.2/libobjc/objc

From: Dan Hitt
Subject: Re: gdnc segfaulting in sarray.h, internal to gcc-3.2/libobjc/objc
Date: 18 May 2003 14:06:56 -0400

Hi Chris,

Thanks for the suggestion to use gcc 3.3.

I've recompiled all of my sources using gcc3.3, and i segfault
in the same place (well, the analogous place in the gcc3.3 source tree).

For reference, i'm using version 1.6.0 of gnustep-base on a red hat 7.3
system (and of course gcc 3.3 per your suggestion).

Thanks again for your advice.


In article <address@hidden>,
Chris B. Vetter <address@hidden> wrote:
>On 13 May 2003 23:49:07 -0400
>address@hidden (Dan Hitt) wrote:
>> As soon as i start up GWorkspace, gdnc segfaults in sarray_get, which
>> is internal to the gcc 3.2 code (gcc-3.2/libobjc/objc/sarray.h,
>> static inline void* sarray_get(struct sarray* array,sidx index)).
>> So: is this some kind of known problem with gcc 3.2?  (I'm using
>> redhat 7.3, but not with the default gcc 2.96 but with 3.2 of August
>> 14, 2002.)
>I'm not sure if it actually is a problem "native" to gcc32 but I've
>seen the exact behaviour only when using gcc32, which made me switch
>to gcc33.
>Though it's labeled 'experimental' I haven't had any problems so far -
>contrary to gcc30 through 32.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]