Here's the result of my sanity testing for M7:
- Bug 312813: [Launch]
Deadlock when terminating a DSF-GDB debug session
- Bug 312817: [Launch] Stack frames don't show up in Debug View for a
DSF-GDB debug session
- Bug 312267: [Debug View] 'Remove All Terminated Launches' is disabled
after a termination
- Bug 312709: [Launch] NPE in GdbLaunchDelegate
- Bug 312629: "[Disassembly] Disassembly toolbar actions should be
disabled when there is no debug context". Note that this is not a
regression.
Please let me know if you have any questions.
- Navid
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf
Of Axel Müller
Sent: Thursday, May 13, 2010 9:48 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] RE: M7 Defect
Did you open a bug? I encounter the same problem. Most of the time when
I
start a DSF-GDB session the Stack and the Variables View is empty.
gdb traces shows:
844,616 13-list-thread-groups
844,618
13^done,groups=[{id="16656",type="process",pid="16656"}]
844,619 (gdb)
844,750 14-list-thread-groups 16656
844,758 14^done,threads=[{id="1",target-id="process
16656",frame={level="0",addr="0x0000000000400945\
",func="main",args=[],file="../src/HelloWorld.cpp",fullname="/home/axel/Programming/eclipse-
ws/runti\
me-
EclipseApplication/HelloWorld/src/HelloWorld.cpp",line="18"},state="stopped"}]
After pressing F8 the debug session continues normally.
964,304 16-exec-continue
I am using M7 with CVS updates on Linux x86_64, GDB 7.0.
Axel
> That is weird.
> Can you open a bug and attach the gdb traces?
>
> ________________________________
> From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Mehregani, Navid Sent: Wednesday, May 12, 2010 3:54 PM
> To: CDT General developers list.
> Subject: [cdt-dev] RE: M7 Defect
>
> >If you refresh the debug view, do the stack frames show up?
>
> No they don't.
>
> ________________________________
> From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Marc Khouzam Sent: Wednesday, May 12, 2010 3:42 PM
> To: 'CDT General developers list.'
> Subject: [cdt-dev] RE: M7 Defect
>
> I haven't seen this before myself.
> If you refresh the debug view, do the stack frames show up?
>
> ________________________________
> From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Mehregani, Navid Sent: Wednesday, May 12, 2010 3:38 PM
> To: CDT General developers list.
> Subject: [cdt-dev] M7 Defect
> I did some sanity testing in M7 and ran into the following issue.
I wanted
> to see if anyone else has seen this before I proceed with a
defect.
>
> I switch between a CDI-GDB and DSF-GDB session several times and
in some
> cases after launching a DSF-GDB session, the stack frame of the
> corresponding session doesn't appear in Debug View. See snapshot
below:
>
>
>
> Terminating the session will result in a workbench hang. The
problem only
> happens intermittently.
>
> On a separate (or perhaps related) note, I also got the following
error
> message:
>
>
> java.lang.ClassCastException:
org.eclipse.cdt.dsf.gdb.launching.GDBDebugger
> cannot be cast to org.eclipse.cdt.debug.core.ICDebugger at
> org.eclipse.cdt.debug.internal.core.DebugConfiguration.createDebugger(Debu
> gConfiguration.java:61) at
>
org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.createCDISession(Lo
> calCDILaunchDelegate.java:466) at
> org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.launchLocalDebugSes
> sion(LocalCDILaunchDelegate.java:145) at
>
org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.launchDebugger(Loca
> lCDILaunchDelegate.java:112) at
>
org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.launch(LocalCDILaun
> chDelegate.java:72) at
>
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigura
> tion.java:853) at
>
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigura
> tion.java:702) at
> org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.j
> ava:923) at
>
org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1126)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
>
> I only got this once and couldn't reproduce it again. However I
can
> reproduce the first issue if I keep launching/terminating a
DSF-GDB
> session.
>
> Please let me know if you've come across either one of these
issues or if
> you know of any outstanding defects that will address them.
>
> Thanks,
> - Navid
>
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev