|
|
|
This thread is locked; no one can reply to it.
|
1
2
|
| Strange error on Allegro upgrade |
|
Elias
Member #358
May 2000
|
9 threads? I find that is too much as well. Either your gdb just is broken, or something is completely wrong. Try running the test program of allegro, and see if everything in it works, and if it also crashes on exit. Really can't think of anything else to try. If all the function in the test program work, but it crashes on exit, i'd say something is wrong with the way atexit() is used. (But I suspect, some of the tests will fail because the vtable is messed up and there is a version conflict after all.) -- |
|
Fabiano Lopes
Member #3,024
December 2002
 |
The same error occurred with:
Seriously, what could be wrong on compiling process? I downloaded the latest Allegro package (4.1.6 WIP), the latest MinGW (3.4.2 Candidate) in a new folder, then I compiled it and I'm getting this annoyance. |
|
Elias
Member #358
May 2000
|
Well, you still didn't answer, is this specific to certain programs, or does it generally happen in every allegro program? I.e. they all work fine, but on exit, it crashes. Or do some crash earlier? Some not crash at all? And compile the debug version of allegro, and also use debugging flags when you compile.. maybe that makes the gdb output more useful. [Edit:] I don't think it has anything to do with compiling, unless it really is that modification you made to the makefile. Anyway, if you can, just try finding out whatever information you can (the two things I said above are just suggestions, don't really know if they will bring any useful info). But since this seems to be such a general bug (all apps crash) it somehow must be something special either with how you compiled allegro, or with your system, since it works for everybody else. -- |
|
Evert
Member #794
November 2000
 |
Quote: The same error occurred with: Also with tests/test.exe? Did you try the debug version of Allegro? Run make clean and make DEBUGMODE=2 from the Allegro directory to rebuild with debugging symbols in place. This should make it easier to debug. Quote: I downloaded the latest Allegro package (4.1.6 WIP) 4.1.16. |
|
Fabiano Lopes
Member #3,024
December 2002
|
EDIT: It seems -mtune=i686 causes the problem. I tried -mtune=i586 (as replacement for -mpentium and it worked fine). |
|
Elias
Member #358
May 2000
|
Hm, might investigate this in any case. Does it also crash with "march=athlon", or whatever is the Duron specific one? I somehow believe this may be related to why /G7 doesn't seem to work with MSVC. -- |
|
Fabiano Lopes
Member #3,024
December 2002
|
Well... no problems if "-mtune=athlon" is used. I switched back to "-mtune=i686" and the bug was back in action (select Quit -> crash). This is something that could be investigated & fixed. |
|
ReyBrujo
Moderator
January 2001
 |
Hmm... maybe you can output the assembler code with and without the switch, though I am not sure if the switch is for compiling or linking optimization. -- |
|
Fabiano Lopes
Member #3,024
December 2002
|
"-mtune=<cpu>" is used during the compiling. |
|
|
1
2
|
This isn't fair... 
Anyway, here's the bug with "i686" option.