| Debug : Cannot step over frame [message #49986] |
Wed, 13 November 2002 18:49  |
Eclipse User |
|
|
|
Originally posted by: ira.greenstein.calebtech.com
I am currently using:
Eclipse 2.0.2 (also 2.0.1)
CDT: 1.0.0
Solaris: 5.8
GDB: 5.2.1
I get the following error when i try to step into or over a line while
debugging:
8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8 <---8<---8<---8<---8<---
!ENTRY org.eclipse.debug.ui 4 5012 Nov 13, 2002 18:09:06.260
!MESSAGE Exceptions occurred attempting to step into the frame
!SUBENTRY 1 org.eclipse.cdt.debug.core 4 5010 Nov 13, 2002 18:09:06.267
!MESSAGE org.eclipse.cdt.debug.core.cdi.CDIException: Timedout
!STACK 0
org.eclipse.cdt.debug.core.cdi.CDIException: Timedout
at
org.eclipse.cdt.debug.mi.core.cdi.CTarget.setCurrentThread(C Target.java:108)
at
org.eclipse.cdt.debug.mi.core.cdi.CThread.stepInto(CThread.j ava:160)
at
org.eclipse.cdt.debug.internal.core.model.CThread.stepInto(C Thread.java:551)
at
org.eclipse.cdt.debug.internal.core.model.CStackFrame.stepIn to(CStackFrame.java:315)
at
org.eclipse.debug.internal.ui.actions.StepIntoActionDelegate .stepAction(StepIntoActionDelegate
java:24)
at
org.eclipse.debug.internal.ui.actions.StepActionDelegate.doA ction(StepActionDelegate.java:18)
at
org.eclipse.debug.internal.ui.actions.AbstractDebugActionDel egate$1.run(AbstractDebugActionDel
egate.java:97)
at
org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:66)
at
org.eclipse.debug.internal.ui.actions.AbstractDebugActionDel egate.run(AbstractDebugActionDeleg
ate.java:92)
at
org.eclipse.ui.internal.PluginAction.runWithEvent(PluginActi on.java:210)
at
org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.j
ava:407)
at
org.eclipse.jface.action.ActionContributionItem.handleWidget Event(ActionContributionItem.java:
361)
at
org.eclipse.jface.action.ActionContributionItem.access$0(Act ionContributionItem.java:352)
at
org.eclipse.jface.action.ActionContributionItem$ActionListen er.handleEvent(ActionContributionI
tem.java:47)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :77)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:853)
8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8 <---8<---8<---8<---8<---
Somtimes i can set another breakpoint further in the code and "continue"
to that point and sometimes it just gives me the same error.
Any clues?
Thanks!
ira
|
|
|
|
| Re: Debug : Cannot step over frame [message #50190 is a reply to message #50016] |
Thu, 14 November 2002 08:30  |
| Eclipse User |
|
|
|
Originally posted by: ira.greenstein.calebtech.com
Igor S. Zamyatin wrote:
> Such message usally appeares when CDT cannot connect to gdb for some
> reasons. Does something similar appear when you start CDT Debug session?
> And try to use gdb(try to use step command) outside Eclipse.
> May be it helps...
> Igor S. Zamyatin
> Interstron Ltd.
> Ira L. Greenstein wrote:
> > I am currently using:
> > Eclipse 2.0.2 (also 2.0.1)
> > CDT: 1.0.0
> > Solaris: 5.8
> > GDB: 5.2.1
> > I get the following error when i try to step into or over a line while
> > debugging:
> > 8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8 <---8<---8<---8<---8<---
> > !ENTRY org.eclipse.debug.ui 4 5012 Nov 13, 2002 18:09:06.260
> > !MESSAGE Exceptions occurred attempting to step into the frame
> > !SUBENTRY 1 org.eclipse.cdt.debug.core 4 5010 Nov 13, 2002 18:09:06.267
> > !MESSAGE org.eclipse.cdt.debug.core.cdi.CDIException: Timedout
> > !STACK 0
> > org.eclipse.cdt.debug.core.cdi.CDIException: Timedout
> > at
> >
org.eclipse.cdt.debug.mi.core.cdi.CTarget.setCurrentThread(C Target.java:108)
> > at
> > org.eclipse.cdt.debug.mi.core.cdi.CThread.stepInto(CThread.j ava:160)
> > at
> >
org.eclipse.cdt.debug.internal.core.model.CThread.stepInto(C Thread.java:551)
> > at
> >
>
org.eclipse.cdt.debug.internal.core.model.CStackFrame.stepIn to(CStackFrame.java:315)
> > at
> >
>
org.eclipse.debug.internal.ui.actions.StepIntoActionDelegate .stepAction(StepIntoActionDelegate
> > java:24)
> > at
> >
>
org.eclipse.debug.internal.ui.actions.StepActionDelegate.doA ction(StepActionDelegate.java:18)
> > at
> >
>
org.eclipse.debug.internal.ui.actions.AbstractDebugActionDel egate$1.run(AbstractDebugActionDel
> > egate.java:97)
> > at
> > org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:66)
> > at
> >
>
org.eclipse.debug.internal.ui.actions.AbstractDebugActionDel egate.run(AbstractDebugActionDeleg
> > ate.java:92)
> > at
> > org.eclipse.ui.internal.PluginAction.runWithEvent(PluginActi on.java:210)
> > at
> >
>
org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.j
> > ava:407)
> > at
> >
>
org.eclipse.jface.action.ActionContributionItem.handleWidget Event(ActionContributionItem.java:
> > 361)
> > at
> >
>
org.eclipse.jface.action.ActionContributionItem.access$0(Act ionContributionItem.java:352)
> > at
> >
>
org.eclipse.jface.action.ActionContributionItem$ActionListen er.handleEvent(ActionContributionI
> > tem.java:47)
> > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :77)
> > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:853)
> > 8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8 <---8<---8<---8<---8<---
> > Somtimes i can set another breakpoint further in the code and "continue"
> > to that point and sometimes it just gives me the same error.
> > Any clues?
> > Thanks!
> > ira
Igor, thanks for the quick reply!
I did try gdb on it's own with no problems. I had some odd behavior this
morning when i restarted eclipse. The debugger performed properly...
once! Then, back to the problem as stated above. As i watched the log in
workspace/.metadata, i could bring up CDT without incident and start the
debugger without incident as well. However, as soon as i tried to step i
saw the exception thrown.
I through the whole thing into truss and found the following:
8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8 <---8<---8<---8<---8<---
8257: door_info(7, 0xFFBE9A68) = 0
8257: door_call(7, 0xFFBE9A50) = 0
8257: Incurred fault #6, FLTBOUNDS %pc = 0xFA49A9E0
8257: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000
8257: Received signal #11, SIGSEGV [caught]
8257: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000
8257: sigprocmask(SIG_SETMASK, 0xFF37F010, 0x00000000) = 0
8257: sigprocmask(SIG_SETMASK, 0xFF38ADE0, 0x00000000) = 0
8257: setcontext(0xFFBEB4E0)
8257: Incurred fault #6, FLTBOUNDS %pc = 0xFA5EFEC0
8257: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000
8257: Received signal #11, SIGSEGV [caught]
8257: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000
8257: sigprocmask(SIG_SETMASK, 0xFF37F010, 0x00000000) = 0
8257: sigprocmask(SIG_SETMASK, 0xFF38ADE0, 0x00000000) = 0
8257: setcontext(0xFFBEAB00)
8257: read(2, "\0", 1) = 1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
8257: read(2, "\0", 1) = 1
8257: read(2, "\0", 1) = 1
8257: Incurred fault #6, FLTBOUNDS %pc = 0xFA5DDF40
8257: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000
8257: poll(0xFA281B58, 0, 10) = 0
8257: Received signal #11, SIGSEGV [caught]
8257: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000
8257: read(2, "\0", 1) = 1
8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8 <---8<---8<---8<---8<---
Also, i forgot to note that i am using j2re1.4.1_01.
Thanks again!
|
|
|
Powered by
FUDForum. Page generated in 0.07847 seconds
Home