Segmentation fault
Is what I get when I try to compile my lighting on one of my map. Other map work well.
Q3Map version 2.5.4 (Mac compile)
What does it mean?
Seam lighting work with 2.3.36…
Maybe it’s me that badly compile 2.5.4? But it works with other map… weird.
Segmentations fault usually appears when you want to access to a forbidden memory area. It may appear when you want to write into the memory, but also when you wzant to read (if you don’t have the rights). Most of time it comes from a bad index in an array, when a program just wants to access further than the size of the array…
I’d think it’s not the compiler’s fault, neither the map’s fault, but your system’s. Maybe you are using windows 98 ? If you are, you should change as soon as possible 
Segmention fault is like an access violation in windows. If you run the map compile in verbose mode, you may get an indication of where it crashes. That might point you to what aspect of your map was making it crash. I have often found that q3map barfs after it has already noticed some problem with the map.
If you compiled q3map2 yourself, you should be able to run the a debugger on it.
You might try getting someone with a windows box to try compiling your map, to see if it is a mac specific bug.
It crash right after it finish loading the different part… Shader, prt, .bsp and .map.
Just like the light thing is about to start, it crash.
Beside that, I tryed other map with it and it works well.
What this map has that the other don’t? No idea.
I’m running Win98SE on my mac beside my OS X… I will try the last Q3Map2 with Win to see…
Tryed to compile the map with the Win version of 2.5.4, and it works well. (Damnly slow since it’s on an emulation, but it works).
What I did that make this particular map to not work on OS X while other map work?
And what I did to 2.5.4 that make it doesn’t work while 2.3.36 work? No idea…
I will have to wait untill someone who know how to debug such thing compile 2.5.4 correctly for the Mac OS X…