https://moythreads.com/wordpress/2009/08/31/debugging-information-in-separate-files/ Abandon All Hope, Ye Who Read This Blog Fri, 14 Aug 2020 20:06:49 +0000 hourly 1 https://wordpress.org/?v=5.1.9 https://moythreads.com/wordpress/2009/08/31/debugging-information-in-separate-files/comment-page-1/#comment-385 Mon, 31 Aug 2009 04:57:17 +0000 http://www.moythreads.com/wordpress/2009/08/31/debugging-information-in-separate-files/#comment-385 t care about optimizations nor the increase in size in the binary and users can always change those flags using CFLAGS when configuring openr2. Is convenient because if my users ever get a core dump, I was able to jump right in and get a useful backtrace and examine the stack. Alternatively they could get the stack trace themselves and send it to me without worrying about anything else than launching gdb with the right arguments. — From the page [...]]]> […] Moy Blog » Blog Archive » Debugging information in separate files http://www.moythreads.com/wordpress/2009/08/31/debugging-information-in-separate-files – view page – cached Debugging information in Linux ELF binaries is usually stored in the binary itself. This had been really convenient to me, for example, I always compile my openr2 library with -ggdb3 -O0. I don’t care about optimizations nor the increase in size in the binary and users can always change those flags using CFLAGS when configuring openr2. Is convenient because if my users ever get a core dump, I was able to jump right in and get a useful backtrace and examine the stack. Alternatively they could get the stack trace themselves and send it to me without worrying about anything else than launching gdb with the right arguments. — From the page […]

]]>