Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] OS X port debugger variables broken

<x-tad-bigger>I'm not familiar with the MI, but here is a section of the trace where the locals are retrieved, but not displayed on the Variables window.</x-tad-bigger><x-tad-bigger>

[1,068,836,027,717] (gdb) </x-tad-bigger>
<x-tad-bigger>
</x-tad-bigger><x-tad-bigger>[1,068,836,027,723] 28-stack-list-frames 0 0</x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>[1,068,836,027,724] 28^done,stack=[frame={level="0",addr="0x00001dd0",fp="0xbffffc60",func="main",fi\</x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>le="hello.C",line="8",dir="/Applications/Eclipse 2.1.2/runtime-workspace/Foo/"}]</x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>[1,068,836,027,725] (gdb) </x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>[1,068,836,027,825] 29-stack-list-arguments 0 0 0</x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>[1,068,836,027,826] 29^done,stack-args=[frame={level="0",args=[{name="argc"},{name="argv"}]}]</x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>[1,068,836,027,827] (gdb) </x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>[1,068,836,027,828] 30-stack-list-locals 0</x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>[1,068,836,027,828] 30^done,locals=[{name="x"}]</x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>[1,068,836,027,829] (gdb) </x-tad-bigger><x-tad-bigger>
</x-tad-bigger>

On Nov 14, 2003, at 9:56 AM, Mikhail Khodjaiants wrote:

The CDT doesn't use the binary parser to display variables. All information
comes from gdb.
You can trace the communication between gdb and CDT. See the topic"Can I
see/log all of the commands which are being driven to gdb?" of CDT FAQ for
details.

----- Original Message -----
From: "Bryan Hunt" <bhunt@xxxxxxx>
To: <cdt-dev@xxxxxxxxxxx>
Sent: Friday, November 14, 2003 10:50 AM
Subject: Re: [cdt-dev] OS X port debugger variables broken


The log file contains no errors. Is the binary parser used for
displaying variables? This is something I don't have working yet.

Bryan

On Nov 11, 2003, at 5:16 PM, Mikhail Khodjaiants wrote:

Check the .log file for errors.

----- Original Message -----
From: "Bryan Hunt" <bhunt@xxxxxxx>
To: <cdt-dev@xxxxxxxxxxx>
Sent: Tuesday, November 11, 2003 12:14 PM
Subject: [cdt-dev] OS X port debugger variables broken


The Variables view in the debugger perspective is not working for me.
I can cursor over a simple int variable and get it's value in a
tool-tip, but it doesn't display in the Variables window - the
Variables window is blank. Any ideas on how to track this down
(breakpoints I could set) would be appreciated.

Bryan

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev



_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev

Back to the top