I hope I can help to shed some light on this issue: There was a discussion on some Ubuntu forum where it was pointed out that this is actually a bug in the 2.6.18 (and newer) kernel: https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.20/+bug/74691
I quickly tested this on a machine where I have a 2.6.18 and a 2.6.17 kernel installed and can confirm that this message doesn't show up with 2.6.17 (2.6.17-2-686 actually). Daniel: Could you please re-route this bug to linux-source-2.6.18 (or the relevant package) if you think my conclusions are right? A recipe to reproduce this problem is: (using a 2.6.18 kernel) * compile a simple program (like hello world): 'gcc -o hello -g hello.c' * open the program in gdb: 'gdb ./hello' * 'break main' * 'run' Now gdb will output: "Starting program: ./hello Failed to read a valid object file image from memory." Note: This allows to debug the program; however single stepping causes gdb to jump pseudo-randomly from one line to another. Also breakpoints are sometimes set somewhere else than expected. If further information is required, I'd be more than happy to provide it. Andreas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
