On 24 Jun 2001 20:07:02 -0700, Justin Erenkrantz wrote: > FWIW, I can't seem to reproduce the problem now. I know that I was > getting odd things last night, but I can't seem to get it to happen > again today. Grr. I feel silly. I could put a note in the STATUS > file that we've seen some oddities with GCC 2.96. I swear I wasn't > making it up - I *was* getting segfaults because it was trying to > allocate too much memory (the size returned from elem_size() was > corrupt).
There was a update to GCC from redhat over the weekend, did you apply that patch perhaps? -- Ian Holsman Performance Measurement and Analysis CNET Networks PH: (415) 364 8608
