[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [dsdp-dd-dev] Problem in debugging with DSF.
|
Ok, I resorted to a hack. The reason behind this
issue is that we are coding for GDB 7 before it is out.
Since that will get fixed before our next release, I
figured a temporary hack for cygwin was ok for a short time.
Dmitri, you can update your org.eclipse.cdt.dsf.gdb
plugin. LaunchUtils.java should change.
Try it out and let me know if it works for
you.
to track the whole GDB versioning
issue.
Marc
Since GDB 7 has not been released yet and the newest GDB
was 6.8, I had to assume that any GDB higher than 6.8
was a built from GDB HEAD which contained GDB 7 features
such as --thread/--frame.
This logic was bound to fail eventually...
Sigh...
In your case, you have a GDB higher than 6.8, but it does
not contain the GDB 7 features...
I'll try to come up
with a workaround...
Hi Pawel and Anton,
I'm using Cygwin gdb.
Here is 'gdb --version' output:
C:\cygwin\bin>gdb
--version
GNU gdb 6.8.0.20080328-cvs
(cygwin-special)
Copyright (C) 2008
Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software:
you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type
"show copying"
and "show warranty"
for details.
This GDB was configured
as "i686-pc-cygwin".
Sincerely,
Dmitri Pikus
From:
| "Leherbauer, Anton"
<Anton.Leherbauer@xxxxxxxxxxxxx>
|
To:
| "Device Debugging developer
discussions" <dsdp-dd-dev@xxxxxxxxxxx>
|
Date:
| 20/01/2009 10:24
|
Subject:
| RE: [dsdp-dd-dev] Problem in
debugging with DSF.
|
Sent by:
| dsdp-dd-dev-bounces@xxxxxxxxxxx |
Dimtry,
it looks like
the gdb you are using does not understand the new --thread option:
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]"
IIRC this option is only available since gdb
version 6.8.50.
The gdb
version is checked before launching the debug session, but this might fail
in your case.
Could you post
the output of gdb --version?
Thanks,
Toni
From: dsdp-dd-dev-bounces@xxxxxxxxxxx
[mailto:dsdp-dd-dev-bounces@xxxxxxxxxxx] On Behalf Of Dmitri Pikus
Sent: Monday, January
19, 2009 2:16 PM
To: Device Debugging developer
discussions
Subject: RE: [dsdp-dd-dev] Problem in debugging with
DSF.
Hi
All,
Following our previous mail exchange, I checked-out DSF
from:
/cvsroot/tools/org.eclipse.cdt/dsf
/cvsroot/tools/org.eclipse.cdt/dsf-gdb
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.
Sincerely,
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 |
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.
See also https://bugs.eclipse.org/bugs/show_bug.cgi?id=251406.
Sorry for any inconvenience.
Regards,
Toni
From: dsdp-dd-dev-bounces@xxxxxxxxxxx
[mailto:dsdp-dd-dev-bounces@xxxxxxxxxxx] On Behalf Of Dmitri Pikus
Sent:
Sunday, January 18, 2009 4:46 PM
To: Device Debugging developer
discussions
Subject: 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:
/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
_______________________________________________
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