Re: Can GCC emit debug information to support debug uninitialized local variables

2010-06-20 Thread asmwarrior
On 2010-6-20 14:18, Ian Lance Taylor wrote: asmwarrior writes: My question is: Is there any possible that GCC can emit some debug information to indicate that one variable is initialed or not.(at least in the DEBUG build mode) You didn't mention which version of gcc you are testing.

Re: Can GCC emit debug information to support debug uninitialized local variables

2010-06-19 Thread asmwarrior
On 2010-6-20 14:18, Ian Lance Taylor wrote: asmwarrior writes: My question is: Is there any possible that GCC can emit some debug information to indicate that one variable is initialed or not.(at least in the DEBUG build mode) You didn't mention which version of gcc you are testing.

Re: Can GCC emit debug information to support debug uninitialized local variables

2010-06-19 Thread Ian Lance Taylor
asmwarrior writes: > My question is: Is there any possible that GCC can emit some debug > information to indicate that one variable is initialed or not.(at > least in the DEBUG build mode) You didn't mention which version of gcc you are testing. With current gcc see if the -fvar-tracking option

Can GCC emit debug information to support debug uninitialized local variables

2010-06-18 Thread asmwarrior
Hi, I have some problem using GCC and GDB, you know, the current GDB has python pretty printer enabled, so that the variables can be show quite nicely. My problem is when gdb try to show some variable that is not initialized. For example: void test() { std::string stdStr("std::string");