Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cdt-dev] RE: M7 Defect

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(DebugConfiguration.java:61)

            at org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.createCDISession(LocalCDILaunchDelegate.java:466)

            at org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.launchLocalDebugSession(LocalCDILaunchDelegate.java:145)

            at org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.launchDebugger(LocalCDILaunchDelegate.java:112)

            at org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.launch(LocalCDILaunchDelegate.java:72)

            at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)

            at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:702)

            at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java: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


Back to the top