Re: debugging strategies

2007-03-23 Thread Robert Connolly
This thread is the same as what you're asking about: http://grsecurity.net/pipermail/grsecurity/2005-October/000581.html It says to run 'paxctl -spm' on the program and libraries, but it sounds like you tried that. CFLAGS="-nopie -fno-pic -norelro -nonow -fno-stack-protector -D_FORTIFY_SOURCE=0"

Re: debugging strategies

2007-03-23 Thread Jan Dvořák
Robert Connolly wrote: > GDB doesn't build, or doesn't work? For me it does build, but fails like this: $ cat >>gdb-test.c < search starts here: /usr/local/include /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include /usr/include End of search list. GNU C version 4.1.1 (i686-pc-linux-gnu) co

Re: debugging strategies

2007-03-23 Thread Robert Connolly
GDB doesn't build, or doesn't work? Robert On Friday March 23 2007 03:11, Rogelio Serrano wrote: > Whats the best debugging strategy for an PIE and ET_DYN system? > > i cant get gdb to work. im being forced to add self test code in all > programs that crash. making them all verbose is not an opti