This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Debugging gnugcc optimized code (O1 or O3) on ar,
- From: "Naval Saini" <navalnovel at gmail dot com>
- To: gdb at sourceware dot org
- Date: Wed, 7 Jan 2009 12:13:06 +0530
- Subject: Debugging gnugcc optimized code (O1 or O3) on ar,
Hi:
We have seen that a gdb issue when debugging an optimized code (-O1 or
-O3), compiled by gnugcc toolchain.
Basically, gdb is unable to keep a track of local variables when the
code is sufficiently complex (depth of function calls is decently
big). At times, a variable can go out of scope without gdb knowing
about it OR it can start displaying incorrect values of the variables
(indicating it is unaware of which variable is present in which
register).
Our sw configuration is following :-
1. gnugcc 4.1.1 toolchain - cross-compiling code for arm V6 (or arm 11)
2. gdb-6.7.1
3. OS - Linux , Library used - uclibc
Regards,
Naval