View Full Version: signal_handler():segment violation

Chex Quest Fan Forums > Tech Support & Computer Discussion > signal_handler():segment violation


Title: signal_handler():segment violation
Description: what does this mean?


SuperZorcher - September 1, 2004 02:00 AM (GMT)
I tryed to load caverens of bazok in legacy and i get that error message. I have been editing the sprites in the wad but not the maps. what does it mean?

edit: It does it with a plain unaltered version of cq to.

NTG56 - September 1, 2004 02:20 AM (GMT)
Legacy messed up. Usually a map error; its possible your sprites dont match the orriginal sprites sizes.

SuperZorcher - September 1, 2004 02:26 AM (GMT)
So if I changed the sprites size it will mess up. hmm Is there anyway to fix this with out having to resize all the frames?

Boingo the Clown - September 1, 2004 03:02 AM (GMT)
If you have been editing the sprites, then there is a good chance you are missing sprites in your edited version.

If Legacy tries to display a sprite that doesn't exist, it will crash with the error you described.

Either you have left out a sprite in the sprite rotation, or you have accidentally saved it with the wrong name. Legacy has no way of knowing that TROIA1 is really supposed to be TROOA1 for example.

SuperZorcher - September 1, 2004 03:11 AM (GMT)
So changing the size won't necciserly make it crash?

NTG56 - September 1, 2004 03:26 AM (GMT)
No, not like the filesize, the grafix dimmensions size. Like if it was 15X15 pixels and you resized it to 30X30 but Legacy still thought it was 15X15 it could get messed up. Boingo is correct also, that error is caused by a lot of things but if u were editing sprites then it makes sense. When do u get the error? Is it when u visit a certain place in the map??

SuperZorcher - September 1, 2004 02:02 PM (GMT)
I did resize the sprite for the flembrane to a smaller size. So Iguess thats it but what odd is is the orginal cq crashs on caverens of bazook too.

NTG56 - September 1, 2004 04:07 PM (GMT)
Hmm.... go check your log.txt and see what happened just before the signal handler thing. Thats what often solves it for me. Try running it with TUCQ as a PWAD.




* Hosted for free by InvisionFree