Menu ▾ ▴

#31 Segfault with GCC 3.0

closed
nobody
None
5
2012-10-09
2001-08-02
Anonymous
No

allegro_init() segmentation faults when compiled under gcc-3.0. It seems to happen because src in ustrzcpy isn't a copy of resource as it should be, but this could mean it's a gcc-3.0 bug. resource contains "allegro.cfg", but src is random. I don't know enough of what's supposed to be going on to really be sure - if one of you could look at it that would be really handy, as I need some of the features of gcc-3.0, and so it would be useful to know whether there was a real problem here.

Discussion

  • Henrik Stokseth

    Henrik Stokseth - 2001-09-13

    Logged In: YES
    user_id=15778

    Does it segfault with optimisations turned off? That's will allow us to localize the problem. It's most likely a gcc optimizer bug.

     

  • Nobody/Anonymous

    Nobody/Anonymous - 2001-09-16

    Logged In: NO

    No it doesn't - good point. I guess it's a compiler optimisation bug then.

     

Log in to post a comment.