[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [dsdp-dd-dev] Problem in debugging with DSF.
|
Hi,
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.
Sorry for any inconvenience.
Regards,
Toni
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:
/cvsroot/tools/org.eclipse.cdt/dsf
/cvsroot/tools/org.eclipse.cdt/dsf-gdb
Compilation of the following projects fails:
org.eclipse.cdt.dsf.ui
org.eclipse.cdt.tests.dsf.gdb
Examples of compilation problems:
In project org.eclipse.cdt.dsf.ui, in class in class
CSourcePresentationCreator:
import
org.eclipse.cdt.ui.text.AsmSourceViewerConfiguration; isn't resolvable,
in my case it's: import
org.eclipse.cdt.internal.ui.editor.asm.AsmSourceViewerConfiguration;
import
org.eclipse.cdt.ui.text.CSourceViewerConfiguration; isn't resolvable
in my case it's: import
org.eclipse.cdt.internal.ui.text.CSourceViewerConfiguration;
etc...
I use CDT from 5.0.1 master update
(cdt-master-5.0.1.zip, files have a date Sept 12, 2008).
Could it be that I use incorrect CDT version?
Thanks in advance,
Sincerely,
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 |
Hi,
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.
Regards,
/fc
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.
Marc
From: dsdp-dd-dev-bounces@xxxxxxxxxxx [mailto:dsdp-dd-dev-bounces@xxxxxxxxxxx] On Behalf Of Pawel Piech
Sent: Thursday,
January 15, 2009 12:40 PM
To: Device Debugging developer
discussions
Subject: 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:
Hi,
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 --->
Environment:
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 (dev.eclipse.org,
/cvsroot/dsdp)
You should
probably take the 1.1.0 official release at
http://download.eclipse.org/dsdp/dd/downloads/.
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
/cvsroot/tools/org.eclipse.cdt/dsf-gdb
Debugged application: simple C application with single
method( main()
) that
contains several printouts.
SCENARIO1:
1. Line breakpoint without actions is set.
2.
Application is debugged with DSF.
Problem1: Threads change to
'Suspended' state, but call stack isn't
shown.
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
box,
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
sent.
If you
can copy paste the commands that match those errors (or the
whole
session
would be great.)
SCENARIO2:
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:
org.eclipse.dd.gdb.internal.provisional.service.command.GDBControlDMCont
ext
incompatible
with
org.eclipse.dd.dsf.debug.service.IRunControl$IExecutionDMContext
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"
Marc
_______________________________________________
dsdp-dd-dev
mailing list
dsdp-dd-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-dd-dev
_______________________________________________
dsdp-dd-dev
mailing list
dsdp-dd-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-dd-dev
_______________________________________________
dsdp-dd-dev mailing
list
dsdp-dd-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-dd-dev