Lots of Segment Faults with grsec 1.9.7d

Discuss and suggest new grsecurity features

Lots of Segment Faults with grsec 1.9.7d

Postby ph0x » Mon Jan 20, 2003 2:56 pm

I've tried to compile Bahamut, among other things, on my slackware box with 2.4.19-grsec (1.9.7d) and I get a lot of Segment Faults.

make[1]: Entering directory `/home/ircd/bahamut-1.4.35/src'
gcc -Wall -g -O2 -DUSE_POLL -I../include -I../zlib -c hash.c
gcc: Internal compiler error: program cc1 got fatal signal 4
make[1]: *** [hash.o] Error 1

It takes me at least 10 tries to complete the compiling of Bahamut, and my distributed.net client crashes randomly with "Segment Fault" error message.

Would it help to upgrade to 2.4.20 and the latest grsec patch?

Thanks in advance,
Andreas
ph0x
 
Posts: 1
Joined: Mon Jan 20, 2003 2:52 pm

Re: Lots of Segment Faults with grsec 1.9.7d

Postby PaX Team » Mon Jan 20, 2003 3:12 pm

ph0x wrote:gcc: Internal compiler error: program cc1 got fatal signal 4
is it always signal 4 (SIGILL)? also, what PaX options are enabled?
Would it help to upgrade to 2.4.20 and the latest grsec patch?
definitely, since it has a newer PaX version in it (and i don't see what else in grsec could be causing this kind of symptoms). if you want to keep 2.4.19 for the time being, you can at least try to apply the latest PaX patch itself and see if that solves the problem (if it does, then you'll have to update to 2.4.20 to use the latest grsec).
PaX Team
 
Posts: 2310
Joined: Mon Mar 18, 2002 4:35 pm


Return to grsecurity development

cron