If the core wasn't dumped on the same machine you are debugging it on you may need to tell gdb the executable to hook up to the code (I think the command line is simply "gdb core /path/to/srcds_i686", switching srcds_i686 for the appropriate platform exe). You may also need to manually set the LD_LIBRARY_PATH before hand (to include the "bin" directory), see the top of srcds_run for the exact line to use.
- Alfred -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Dance Sent: Wednesday, April 13, 2005 8:00 AM To: [email protected] Subject: [hlcoders] Linux - Debugging srcds Core Dumps Hi, I've been having a hell of a time trying to debug a core dump. Everything works well if you run srcds through gdb, you can get a backtrace with symbols and everything. But core dumps don't work at all -- there are no symbols for the crash (you just get memory addresses and question marks). I've tried many things, but from what I've read "gdb core" should do everything necessary to load the SOs and the binary. So, does anyone know how to debug a core dump from srcds? Thanks, --JD _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
