[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Potential Bug in CDT Variables Tab
|
This looks like bug 328573. Under certain circumstances gdb returns multiple variables with the same name within the same stack frame. Normally that happens if a local scope hides a variable in the parent scope.
The question now is whether you use DSF or CDI. For DSF, this should be fixed, for CDI I don't know.
Open the launch configuration dialog and select your launch configuration. If the bottom of the page says something like "Using GDB (DSF)...", you are using DSF, and your problem is a bug that should be reported and investigated.
Otherwise you are using CDI and you just might want to select DSF.
Jens.
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Jason Litton
> Sent: Dienstag, 31. Januar 2012 18:33
> To: cdt-dev@xxxxxxxxxxx
> Subject: [cdt-dev] Potential Bug in CDT Variables Tab
>
> Hello,
> I believe I have discovered a bug in CDT views. I was trying to set
> watchpoints in a ram stage debug, and I got doubled variables in the
> variable view (see attached screen shot). If I try to click on one of
> these variables in order to set a watchpoint, the highlighting flickers
> rapidly between the two variables and a watchpoint can't be set. The code
> being debugged looks like:
>
> void foo(int boot_complete);
>
> void foo(int boot_complete)
> {
> //do stuff
> }
>
> Looking at a GDB console, I can see that GDB is only aware of one variable
> named boot_complete, so it appears there's something strange in the CDT
> handling code. I was just wondering if this is a known issue or if it's
> something that a bug should be filed on.
>
> Thanks,
> Jason Litton
