This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: gdb says EVERY argument or variable is optimized out (Re: gdb and fission scheme (gcc: -gsplit-dwarf, gnu ld gold :--gdb-index ))
- From: "ISHIKAWA,chiaki" <ishikawa at yk dot rim dot or dot jp>
- To: Andrew Burgess <andrew dot burgess at embecosm dot com>
- Cc: gdb at sourceware dot org
- Date: Thu, 29 Jan 2015 03:46:49 +0900
- Subject: Re: gdb says EVERY argument or variable is optimized out (Re: gdb and fission scheme (gcc: -gsplit-dwarf, gnu ld gold :--gdb-index ))
- Authentication-results: sourceware.org; auth=none
- Authentication-results: access07.SiriusCloud.jp; dkim=none (no signature) header.i=unknown; x-dkim-adsp=none (insecure policy)
- References: <5331159C dot 1040906 at yk dot rim dot or dot jp> <54BC7345 dot 3050307 at yk dot rim dot or dot jp> <20150126084832 dot GK27990 at embecosm dot com>
On 2015/01/26 17:48, Andrew Burgess wrote:
* ISHIKAWA,chiaki <ishikawa@yk.rim.or.jp> [2015-01-19 12:00:21 +0900]:
However, for debugging particular class of bugs,
I really needed to print some values on the stack trace when a
breakpoint is hit, as well as local variables manually.
So I made sure that I passed -O instead of higher optimization.
-O is not "no optimisation", do you get better debugging with -O0 ?
This might be it!
I will check and report next week.
In my case, disabling -gsplit-dwarf means a very long time (several
minutes) of I/O during linking process alone and this is unacceptable
overhead for interactive debugging after changing a single C++
source file.
OK, but you could try it one time and see if it fixes your problem.
That would narrow down where the bug is coming from....
I will try it once also as well as -O0 above and report back.
with -gsplit-dwarf and -O0
without -gsplit-dwarf and {-O,-O0}
[Oh wait, I got a better symbol handling the year before, and I think
I used -O instead of -O0. Well, let me try anyway afresh and report back.]
Thank you for the hints!
TIA
Thanks,
Andrew