debugging programs

debugging programs

Post by Derek Snid » Sun, 06 Nov 1994 15:37:56

Is there a way to control how linux/gcc sets its protections on memory and

It seems that it is possible for a program, via bad pointer operations,
to modify its own code.  Is there a way to prevent this, and to cause a
segmentation fault so that the faulty code may be found?

I have a program that seems to occasionally generate ILLEGAL INSTRUCTION
errors... and Linux claims that this could be due to self modifying code.

 Telnet to our mud ... Realms of Despair ---> 4000
Or join our International Teleconference ---> 9000