sys-devel/gdb attempts to access files in /var/tmp/portage (long since deleted) when issued a 'list' command. Reproducible: Always Steps to Reproduce: 1. I open my battle executable (personal project) 2. Issue 'list' 3. Actual Results: michael@camille ourrpg $ gdb battle GNU gdb 6.7.1 Copyright (C) 2007 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"... Using host libthread_db library "/lib/libthread_db.so.1". (gdb) list 1 /var/tmp/portage/sys-libs/glibc-2.5-r4/work/build-default-i686-pc-linux-gnu-linuxthreads/csu/crti.S: No such file or directory. in /var/tmp/portage/sys-libs/glibc-2.5-r4/work/build-default-i686-pc-linux-gnu-linuxthreads/csu/crti.S (gdb)
you built things with -g and so the file paths contained in the debug data refers to where the source files were when compiled -- in /var/tmp/portage
How do I build things without -g? I just use emerge...
-g is a CFLAG. if you didnt use it, it may just always happen. either way, it isnt a bug, it's expected behavior.
How do I fix it?
why dont you actually run to a file you care about. when you first run an ELF application, the entry point is the crt code of glibc. this is not a bug, this is exactly how it's supposed to be. do a "b main" and run to your main function or wherever and then do a list *from that context*. if you need help using gdb, please ask on the forums. bugzilla is not a support forum.
