SIGSEGVs with g++3.2

Benjamin Kosnik bkoz@redhat.com
Fri Aug 2 09:31:00 GMT 2002


> According to Gwenole Beauchesne this is the case with 3.1.0 and 3.1.1
> too, ie. IMHO not a show stopper for 3.2.

I'm not familiar with this, but the __loc argument looks suspect in the
reported stack trace.

Could one of you please send me a self-contained testcase (minimal) that
reproduces this issue? Also, enter it in GNATS?

thanks,
benjamin



More information about the Gcc mailing list