Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [dsdp-dd-dev] Problem in debugging with DSF.

Hi All,

Following our previous mail exchange, I checked-out DSF from:

and CDT from: /cvsroot/tools/org.eclipse.cdt/all

I get the same error as in original mail when running it.

a) Console:
New thread 9356.0x23a0]
[New thread 9356.0x2330]
mi_cmd_stack_info_depth: Usage: [MAX_DEPTH]
mi_cmd_stack_list_frames: Usage: [FRAME_LOW FRAME_HIGH]
mi_cmd_stack_info_depth: Usage: [MAX_DEPTH]

b) Nothing is printed to '<workspace>/.metadata/.log'.

c) I enabled tracing in plugin 'org.eclipse.cdt.dsf.gdb' (that is, as I understand, corresponds to 'org.eclipse.dd.mi' plugin from release 1.1.0).
Trace is enclosed in 'trace.txt' file.

Dmitri Pikus

From: "Leherbauer, Anton" <Anton.Leherbauer@xxxxxxxxxxxxx>
To: "Device Debugging developer discussions" <dsdp-dd-dev@xxxxxxxxxxx>
Date: 19/01/2009 09:49
Subject: RE: [dsdp-dd-dev] Problem in debugging with DSF.
Sent by: dsdp-dd-dev-bounces@xxxxxxxxxxx

to compile the migrated DSF plug-ins you need CDT from CVS HEAD.
Some internal classes and interfaces moved to API packages since CDT 5.0.x.
See also
Sorry for any inconvenience.

From: dsdp-dd-dev-bounces@xxxxxxxxxxx [mailto:dsdp-dd-dev-bounces@xxxxxxxxxxx] On Behalf Of Dmitri Pikus
Sunday, January 18, 2009 4:46 PM
Device Debugging developer discussions
Re: [dsdp-dd-dev] Problem in debugging with DSF.

Hi All,

Thanks for responses!

1. I tried the official release of Device Debug 1.1.0 Release Build from 8.12.2008 (DSF SDK + DSF GDB-MI + DSF GDB-Launch), and I got the same result as described in original mail, Problem 1, Scenario 1.

Corresponding '<workspace>/.metadata/.log' is included:


2. To enable tracing, I checked-out DSF plugins from new location mentioned:



Compilation of the following projects fails:



Examples of compilation problems:

In project org.eclipse.cdt.dsf.ui, in class in class

org.eclipse.cdt.ui.text.AsmSourceViewerConfiguration; isn't resolvable,
in my case it's:
import org.eclipse.cdt.internal.ui.editor.asm.AsmSourceViewerConfiguration;

org.eclipse.cdt.ui.text.CSourceViewerConfiguration; isn't resolvable
in my case it's:  
import org.eclipse.cdt.internal.ui.text.CSourceViewerConfiguration;


I use CDT from 5.0.1 master update (, files have a date Sept 12, 2008).
Could it be that I use incorrect CDT version?

Thanks in advance,

Dmitri Pikus

From: Francois Chouinard <fchouinard@xxxxxxxxx>
To: Device Debugging developer discussions <dsdp-dd-dev@xxxxxxxxxxx>
Date: 15/01/2009 22:01
Subject: Re: [dsdp-dd-dev] Problem in debugging with DSF.
Sent by: dsdp-dd-dev-bounces@xxxxxxxxxxx


About the breakpoint action issue: there was a small mishap when the contexts structure were re-factored for multi-process support and that case unfortunately fell through the cracks.

Marc and I made a quick patch and it tested OK.

I opened Bug261258 and I will post the fix shortly.


On Thu, Jan 15, 2009 at 1:33 PM, Marc Khouzam <
marc.khouzam@xxxxxxxxxxxx> wrote:
Hi again,


with Francois' help we tested actions again (we do support them, sorry) and reproduced the class cast exception.

I will look into it.



From: dsdp-dd-dev-bounces@xxxxxxxxxxx [mailto:dsdp-dd-dev-bounces@xxxxxxxxxxx] On Behalf Of Pawel Piech
Thursday, January 15, 2009 12:40 PM
Device Debugging developer discussions
Re: [dsdp-dd-dev] Problem in debugging with DSF.

A full copy of the log found in <workspace>/.metadata/.log would be very helpful too.

Marc Khouzam wrote:


see below for anwers.

From: Dmitri Pikus
Sent: Thursday, January 15, 2009 10:36 AM
Subject: [dsdp-dd-dev] Problem in debugging with DSF.

<--- PROBLEM1 --->

OS: Windows XP Professional, SP2.
I don't have acces to that environment so I won't be able to try out
your test.
But we can try to address it by email only.

Eclipse: 3.4.1
CDT: 5.0.1
DSF: 1.1.0 - latest plugins taken from CVS (,

You should probably take the 1.1.0 official release at
The latest plugins are most probably fine but in rare cases may not
always work.
Also, for your info, DSF has migrated to CDT so the plugins will
continue to elvolve in
/cvsroot/tools/org.eclipse.cdt/dsf and

Debugged application: simple C application with single method( main()
) that contains several printouts.
1. Line breakpoint without actions is set.
2. Application is debugged with DSF.

Problem1: Threads change to 'Suspended' state, but call stack isn't
Problem2: Line with reached breakpoint isn't colored.
Problem3: The following mesages are displayed in console:
mi_cmd_stack_info_depth: Usage: [MAX_DEPTH]
mi_cmd_stack_list_frames: Usage: [FRAME_LOW FRAME_HIGH]
mi_cmd_stack_info_depth: Usage: [MAX_DEPTH]
Since you have the plugins checked-out, you can enable tracing so we can
see the commands.
Before you launch the eclipse that will run DSF, go to your launch
configuration and
select the Tracing tab.  Find the plugin org.eclipse.dd.mi and check the
as well as the debug box on the right-hand panel for that plugin.
You can then reproduce this and you will see the commands that are being
If you can copy paste the commands that match those errors (or the whole
would be great.)

1. Line breakpoint with Resume action is set.
I don't think we support Actions yet.

2. Application is debugged with DSF.
Problem: ClassCastException happens:

ext incompatible with
Changing GDBControlDMContext class to implement IExecutionDMContext
doesn't help much:
I see problems 1 and 2 as in scenario 1, and message
'mi_cmd_stack_info_depth: Usage: [MAX_DEPTH]' is displayed.

GDBControlDMContext is no longer an IExecutionDMContext, ever since we
started to support multi-process debugging.
Obviously, there is a case where the use of GDBControlDMContext has not
been replaced.
Do you have the stack dump of the exception?

<--- PROBLEM1 --->
Update Policy selection not showing in the variables view menu.
If you want to use update policies, you have to enable them using
Window->Customize Perspective... and should enable the checkbox for
"Debug Update Modes"

dsdp-dd-dev mailing list


dsdp-dd-dev mailing list


dsdp-dd-dev mailing list

dsdp-dd-dev mailing list

Configuration location:
Configuration file:
    file:/C:/dev/eclipse3.4.1_workspaces/ws2/.metadata/.plugins/org.eclipse.pde.core/runtime-ws2/config.ini loaded
Install location:
Framework located:
Framework classpath:
Splash location:
Debug options:
    file:/C:/dev/eclipse3.4.1_workspaces/ws2/.metadata/.plugins/org.eclipse.pde.core/runtime-ws2/.options loaded
Time to load bundles: 16
Starting application: 1266
Application Started: 9063
498,578 1source .gdbinit
498,593 &"source .gdbinit\n"
498,593 &".gdbinit: No such file or directory.\n"
498,593 1^error,msg=".gdbinit: No such file or directory."
498,609 (gdb) 
498,609 2-file-exec-and-symbols C:/dev/eclipse3.4.1_workspaces/runtime-ws2/test1/Debug/test1.exe
498,625 2^done
498,625 (gdb) 
498,625 3-environment-cd C:/dev/eclipse3.4.1_workspaces/runtime-ws2/test1
498,625 3^done
498,625 (gdb) 
498,656 4-gdb-set auto-solib-add on
498,656 4^done
498,656 (gdb) 
498,671 5-environment-directory C:/dev/eclipse3.4.1_workspaces/runtime-ws2/test1 C:/dev/eclipse3.4.1_workspaces/runtime-ws2/test1/Debug C:/dev/eclipse3.4.1_workspaces/runtime-ws2/test1/Debug/src C:/dev/eclipse3.4.1_workspaces/runtime-ws2/test1/src
498,671 5^done,source-path="C:/dev/eclipse3.4.1_workspaces/runtime-ws2/test1:C:/dev/eclipse3.4.1_workspaces/runtime-ws2/test1/Debug:C:/dev/eclipse3.4.1_workspaces/runtime-ws2/test1/Debug/src:C:/dev/eclipse3.4.1_workspaces/runtime-ws2/test1/src:$cdir:$cwd"
498,671 (gdb) 
498,687 6-break-insert /cygdrive/c/dev/eclipse3.4.1_workspaces/runtime-ws2/test1/src/test1.c:15
498,703 6^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x0040107a",func="main",file="../src/test1.c",fullname="/cygdrive/c/dev/eclipse3.4.1_workspaces/runtime-ws2/test1/src/test1.c",line="15",times="0"}
498,718 (gdb) 
498,734 7-break-insert -t main
498,734 7^done,bkpt={number="2",type="breakpoint",disp="del",enabled="y",addr="0x00401075",func="main",file="../src/test1.c",fullname="/cygdrive/c/dev/eclipse3.4.1_workspaces/runtime-ws2/test1/src/test1.c",line="14",times="0"}
498,734 (gdb) 
498,734 8-exec-run
498,734 8^running
498,734 (gdb) 
498,734 ~"[New thread 8472.0x24e8]\n"
498,812 ~"[New thread 8472.0x2054]\n"
498,843 8*stopped,thread-id="1",frame={addr="0x00401075",func="main",args=[],file="../src/test1.c",fullname="/cygdrive/c/dev/eclipse3.4.1_workspaces/runtime-ws2/test1/src/test1.c",line="14"}
498,843 (gdb) 
498,953 9-thread-list-ids
498,953 9^done,thread-ids={thread-id="2",thread-id="1"},number-of-threads="2"
498,953 (gdb) 
498,968 10-stack-info-depth --thread 1 11
498,968 &"mi_cmd_stack_info_depth: Usage: [MAX_DEPTH]\n"
498,968 10^error,msg="mi_cmd_stack_info_depth: Usage: [MAX_DEPTH]"
498,968 (gdb) 
498,984 11-stack-list-frames --thread 1 0 1
498,984 &"mi_cmd_stack_list_frames: Usage: [FRAME_LOW FRAME_HIGH]\n"
498,984 11^error,msg="mi_cmd_stack_list_frames: Usage: [FRAME_LOW FRAME_HIGH]"
498,984 (gdb) 
499,000 12info threads
499,000 &"info threads\n"
499,000 ~"  2 thread 8472.0x2054  0x7c90eb94 in ntdll!LdrAccessResource ()\n"
499,000 ~"   from /cygdrive/c/WINDOWS/system32/ntdll.dll\n"
499,000 ~"* 1 thread 8472.0x24e8  main () at ../src/test1.c:14\n"
499,000 12^done
499,000 (gdb) 
499,140 13-stack-info-depth --thread 2 11
499,156 &"mi_cmd_stack_info_depth: Usage: [MAX_DEPTH]\n"
499,156 13^error,msg="mi_cmd_stack_info_depth: Usage: [MAX_DEPTH]"
499,156 (gdb) 

Back to the top