Home » Language IDEs » C / C++ IDE (CDT) » Problem of eclipse when interpreting debugger output
| Problem of eclipse when interpreting debugger output [message #113827] |
Wed, 04 August 2004 09:30  |
Eclipse User |
|
|
|
Originally posted by: e.egberts.tantec.de
Hello,
in my project there are breakpoints that didn't work proper - they stop
but eclipse failed in any debugging function, like showing informations
about local environment or stepping. Eclipse only reports "<Stack is not
available: Cannot access memory at address 0x1.>" (or other adresses).
Debugging the same breakpoints using GDB without eclipse shows this
error to be only the "root message" of backtrace info. All informations
are available and also stepping is possible.
The backtrace looks like this:
[...]
#16 0x00445355 in _Z7WndProcP&HWND__jjl@16 ()
#17 0x77e7124c in _libwsock32_a_iname ()
#18 0x00780039 in ?? ()
Cannot access memory at address 0x1
I think backtrace stops because of entering protected system area and
eclipse handles it as a general failure. Is this a known bug or does
anyone know a workaround to let eclipse jump over the error message?
Best regards,
Ed
|
|
| | | | | |
| Re: Problem of eclipse when interpreting debugger output [message #114211 is a reply to message #114182] |
Thu, 05 August 2004 11:43  |
| Eclipse User |
|
|
|
Originally posted by: e.egberts.tantec.de
> And, please, post your log.
Okay, thats it. Start, going directly to error and exit.
The output of GDB that leads to the problem is described in root message
of thread.
HTH,
Ed
!SESSION Aug 05, 2004 17:35:50.311
---------------------------------------------
eclipse.buildId=I200406251208
java.version=1.4.2_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
!ENTRY org.eclipse.osgi Aug 05, 2004 17:36:33.463
!MESSAGE Error while stopping "org.eclipse.cdt.debug.ui_2.0.0".
!STACK 0
org.osgi.framework.BundleException: Exception in
org.eclipse.cdt.debug.ui.CDebugUIPlugin.stop() of bundle
org.eclipse.cdt.debug.ui.
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s top(BundleContextImpl.java:1010)
at
org.eclipse.osgi.framework.internal.core.BundleHost.stopWork er(BundleHost.java:502)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.stop (AbstractBundle.java:437)
at
org.eclipse.core.runtime.adaptor.BundleStopper.basicStopBund les(BundleStopper.java:75)
at
org.eclipse.core.runtime.adaptor.BundleStopper.stopBundles(B undleStopper.java:62)
at
org.eclipse.core.runtime.adaptor.EclipseAdaptor.frameworkSto pping(EclipseAdaptor.java:551)
at
org.eclipse.osgi.framework.internal.core.Framework.shutdown( Framework.java:457)
at
org.eclipse.osgi.framework.internal.core.SystemBundle$1.run( SystemBundle.java:182)
at java.lang.Thread.run(Unknown Source)
Caused by: org.eclipse.swt.SWTException: Device is disposed
at org.eclipse.swt.SWT.error(SWT.java:2691)
at org.eclipse.swt.SWT.error(SWT.java:2616)
at org.eclipse.swt.SWT.error(SWT.java:2587)
at org.eclipse.swt.widgets.Display.error(Display.java:736)
at org.eclipse.swt.widgets.Display.asyncExec(Display.java:525)
at
org.eclipse.cdt.debug.ui.CDebugUIPlugin.listenSelection(CDeb ugUIPlugin.java:345)
at org.eclipse.cdt.debug.ui.CDebugUIPlugin.stop(CDebugUIPlugin. java:325)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$2 .run(BundleContextImpl.java:994)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s top(BundleContextImpl.java:990)
... 8 more
Root exception:
org.eclipse.swt.SWTException: Device is disposed
at org.eclipse.swt.SWT.error(SWT.java:2691)
at org.eclipse.swt.SWT.error(SWT.java:2616)
at org.eclipse.swt.SWT.error(SWT.java:2587)
at org.eclipse.swt.widgets.Display.error(Display.java:736)
at org.eclipse.swt.widgets.Display.asyncExec(Display.java:525)
at
org.eclipse.cdt.debug.ui.CDebugUIPlugin.listenSelection(CDeb ugUIPlugin.java:345)
at org.eclipse.cdt.debug.ui.CDebugUIPlugin.stop(CDebugUIPlugin. java:325)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$2 .run(BundleContextImpl.java:994)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s top(BundleContextImpl.java:990)
at
org.eclipse.osgi.framework.internal.core.BundleHost.stopWork er(BundleHost.java:502)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.stop (AbstractBundle.java:437)
at
org.eclipse.core.runtime.adaptor.BundleStopper.basicStopBund les(BundleStopper.java:75)
at
org.eclipse.core.runtime.adaptor.BundleStopper.stopBundles(B undleStopper.java:62)
at
org.eclipse.core.runtime.adaptor.EclipseAdaptor.frameworkSto pping(EclipseAdaptor.java:551)
at
org.eclipse.osgi.framework.internal.core.Framework.shutdown( Framework.java:457)
at
org.eclipse.osgi.framework.internal.core.SystemBundle$1.run( SystemBundle.java:182)
at java.lang.Thread.run(Unknown Source)
|
|
|
| Re: Problem of eclipse when interpreting debugger output [message #114215 is a reply to message #114211] |
Thu, 05 August 2004 12:48 |
| Eclipse User |
|
|
|
Originally posted by: mikhailk.qnx.com
This is a known problem, it doesn't affect debugging at all and has nothing
to do with your problems. It happens when Eclipse shuts down one of the CDT
debugger plugins..
"Edzard Egberts" <e.egberts@tantec.de> wrote in message
news:cetk9g$5ur$1@eclipse.org...
>
> > And, please, post your log.
>
> Okay, thats it. Start, going directly to error and exit.
> The output of GDB that leads to the problem is described in root message
> of thread.
>
> HTH,
>
> Ed
>
>
> !SESSION Aug 05, 2004 17:35:50.311
> ---------------------------------------------
> eclipse.buildId=I200406251208
> java.version=1.4.2_04
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
>
> !ENTRY org.eclipse.osgi Aug 05, 2004 17:36:33.463
> !MESSAGE Error while stopping "org.eclipse.cdt.debug.ui_2.0.0".
> !STACK 0
> org.osgi.framework.BundleException: Exception in
> org.eclipse.cdt.debug.ui.CDebugUIPlugin.stop() of bundle
> org.eclipse.cdt.debug.ui.
> at
>
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s top(BundleContex
tImpl.java:1010)
> at
>
org.eclipse.osgi.framework.internal.core.BundleHost.stopWork er(BundleHost.ja
va:502)
> at
>
org.eclipse.osgi.framework.internal.core.AbstractBundle.stop (AbstractBundle.
java:437)
> at
>
org.eclipse.core.runtime.adaptor.BundleStopper.basicStopBund les(BundleStoppe
r.java:75)
> at
>
org.eclipse.core.runtime.adaptor.BundleStopper.stopBundles(B undleStopper.jav
a:62)
> at
>
org.eclipse.core.runtime.adaptor.EclipseAdaptor.frameworkSto pping(EclipseAda
ptor.java:551)
> at
>
org.eclipse.osgi.framework.internal.core.Framework.shutdown( Framework.java:4
57)
> at
>
org.eclipse.osgi.framework.internal.core.SystemBundle$1.run( SystemBundle.jav
a:182)
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.eclipse.swt.SWTException: Device is disposed
> at org.eclipse.swt.SWT.error(SWT.java:2691)
> at org.eclipse.swt.SWT.error(SWT.java:2616)
> at org.eclipse.swt.SWT.error(SWT.java:2587)
> at org.eclipse.swt.widgets.Display.error(Display.java:736)
> at org.eclipse.swt.widgets.Display.asyncExec(Display.java:525)
> at
>
org.eclipse.cdt.debug.ui.CDebugUIPlugin.listenSelection(CDeb ugUIPlugin.java:
345)
> at org.eclipse.cdt.debug.ui.CDebugUIPlugin.stop(CDebugUIPlugin. java:325)
> at
>
org.eclipse.osgi.framework.internal.core.BundleContextImpl$2 .run(BundleConte
xtImpl.java:994)
> at java.security.AccessController.doPrivileged(Native Method)
> at
>
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s top(BundleContex
tImpl.java:990)
> ... 8 more
> Root exception:
> org.eclipse.swt.SWTException: Device is disposed
> at org.eclipse.swt.SWT.error(SWT.java:2691)
> at org.eclipse.swt.SWT.error(SWT.java:2616)
> at org.eclipse.swt.SWT.error(SWT.java:2587)
> at org.eclipse.swt.widgets.Display.error(Display.java:736)
> at org.eclipse.swt.widgets.Display.asyncExec(Display.java:525)
> at
>
org.eclipse.cdt.debug.ui.CDebugUIPlugin.listenSelection(CDeb ugUIPlugin.java:
345)
> at org.eclipse.cdt.debug.ui.CDebugUIPlugin.stop(CDebugUIPlugin. java:325)
> at
>
org.eclipse.osgi.framework.internal.core.BundleContextImpl$2 .run(BundleConte
xtImpl.java:994)
> at java.security.AccessController.doPrivileged(Native Method)
> at
>
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s top(BundleContex
tImpl.java:990)
> at
>
org.eclipse.osgi.framework.internal.core.BundleHost.stopWork er(BundleHost.ja
va:502)
> at
>
org.eclipse.osgi.framework.internal.core.AbstractBundle.stop (AbstractBundle.
java:437)
> at
>
org.eclipse.core.runtime.adaptor.BundleStopper.basicStopBund les(BundleStoppe
r.java:75)
> at
>
org.eclipse.core.runtime.adaptor.BundleStopper.stopBundles(B undleStopper.jav
a:62)
> at
>
org.eclipse.core.runtime.adaptor.EclipseAdaptor.frameworkSto pping(EclipseAda
ptor.java:551)
> at
>
org.eclipse.osgi.framework.internal.core.Framework.shutdown( Framework.java:4
57)
> at
>
org.eclipse.osgi.framework.internal.core.SystemBundle$1.run( SystemBundle.jav
a:182)
> at java.lang.Thread.run(Unknown Source)
|
|
|
| Re: Problem of eclipse when interpreting debugger output [message #114294 is a reply to message #114215] |
Thu, 05 August 2004 13:44 |
| Eclipse User |
|
|
|
Originally posted by: e.egberts.tantec.de
Hello,
> This is a known problem, it doesn't affect debugging at all
ups, I'm sorry.
But now I succeded in debugging window. It was a stupid problem of
filename starting with "." :o/
Cutting out the successful parts, the problem is shown below.
"info threads" is the last order working without problems.
"17-stack-info-depth" seems to be "info stack 17" and finishes with
"Cannot access memory...".
"Bt" tells me, frames are ending at #5:
(gdb) bt
#0 cb_Close(Fl_Widget*, void*) (w=0x910920, o=0x0) at ../Main.cpp:18
#1 0x0040601a in Fl::handle(int, Fl_Window*) ()
#2 0x00405ee6 in Fl::handle(int, Fl_Window*) ()
#3 0x0040acdf in _Z7WndProcP6HWND__jjl@16 ()
#4 0x77e7124c in _libwsock32_a_iname ()
#5 0x00010001 in ?? () Cannot access memory at address 0x1b
The Output of Eclipse:
[1.091.726.138.622] 16 info threads
[1.091.726.138.632] &"info threads\n"
[1.091.726.138.642] ~" 2 thread 244.0x102 "
[1.091.726.138.652] ~"* 1 thread 244.0x93 "
[1.091.726.138.692]
16^done,frame={addr="0x77f77fa7",func="??",args=[]},frame={f
unc="cb_Close(Fl_Wid\
get*,
void*)",args=[{name="w",value="0x910920"},{name="o",value= "0x0"}],file="..
/Main.cpp",line="18"\
}
[1.091.726.138.742] (gdb)
[1.091.726.138.762] 17-stack-info-depth
[1.091.726.138.772] &"Cannot access memory at address 0x1b\n"
[1.091.726.138.782] 17^error,msg="Cannot access memory at address 0x1b"
[1.091.726.138.792] (gdb)
[1.091.726.138.802] 17-stack-info-depth
[1.091.726.138.842] &"Cannot access memory at address 0x1b\n"
[1.091.726.138.842] 17^error,msg="Cannot access memory at address 0x1b"
[1.091.726.138.852] (gdb)
[1.091.726.138.882] 18-stack-info-depth
[1.091.726.138.892] &"Cannot access memory at address 0x1b\n"
[1.091.726.138.902] 18^error,msg="Cannot access memory at address 0x1b"
[1.091.726.138.912] 18-stack-info-depth
[1.091.726.138.932] (gdb)
[1.091.726.139.323] &"Cannot access memory at address 0x1b\n"
[1.091.726.139.323] 18^error,msg="Cannot access memory at address 0x1b"
[1.091.726.139.333] (gdb)
It seems to me looking for frames in the wrong direction? ;o)
This causes a kind of error status, and the debugger is not able to step
or watch something, but can continue or suspend.
Also a known Problem?
Ed
|
|
|
| Re: Problem of eclipse when interpreting debugger output [message #114318 is a reply to message #114294] |
Thu, 05 August 2004 14:01 |
| Eclipse User |
|
|
|
Originally posted by: mikhailk.qnx.com
Well, your program stops in gdb for some reason and gdb reports an error.
What are you expecting in this situation?
And what do you mean by "It seems to me looking for frames in the wrong
direction"? "stack-info-depth" is supposed to return the number of frames,
which is 5 according to backtrace result. Maybe, it's a known problem in
gdb.
"Edzard Egberts" <e.egberts@tantec.de> wrote in message
news:cetrc7$iju$1@eclipse.org...
> Hello,
>
> > This is a known problem, it doesn't affect debugging at all
>
> ups, I'm sorry.
>
> But now I succeded in debugging window. It was a stupid problem of
> filename starting with "." :o/
>
> Cutting out the successful parts, the problem is shown below.
> "info threads" is the last order working without problems.
> "17-stack-info-depth" seems to be "info stack 17" and finishes with
> "Cannot access memory...".
>
> "Bt" tells me, frames are ending at #5:
> (gdb) bt
> #0 cb_Close(Fl_Widget*, void*) (w=0x910920, o=0x0) at ../Main.cpp:18
> #1 0x0040601a in Fl::handle(int, Fl_Window*) ()
> #2 0x00405ee6 in Fl::handle(int, Fl_Window*) ()
> #3 0x0040acdf in _Z7WndProcP6HWND__jjl@16 ()
> #4 0x77e7124c in _libwsock32_a_iname ()
> #5 0x00010001 in ?? () Cannot access memory at address 0x1b
>
> The Output of Eclipse:
>
> [1.091.726.138.622] 16 info threads
> [1.091.726.138.632] &"info threads\n"
> [1.091.726.138.642] ~" 2 thread 244.0x102 "
> [1.091.726.138.652] ~"* 1 thread 244.0x93 "
> [1.091.726.138.692]
> 16^done,frame={addr="0x77f77fa7",func="??",args=[]},frame={f
> unc="cb_Close(Fl_Wid\
> get*,
> void*)",args=[{name="w",value="0x910920"},{name="o",value= "0x0"}],file="..
> /Main.cpp",line="18"\
> }
> [1.091.726.138.742] (gdb)
> [1.091.726.138.762] 17-stack-info-depth
> [1.091.726.138.772] &"Cannot access memory at address 0x1b\n"
> [1.091.726.138.782] 17^error,msg="Cannot access memory at address 0x1b"
> [1.091.726.138.792] (gdb)
> [1.091.726.138.802] 17-stack-info-depth
> [1.091.726.138.842] &"Cannot access memory at address 0x1b\n"
> [1.091.726.138.842] 17^error,msg="Cannot access memory at address 0x1b"
> [1.091.726.138.852] (gdb)
> [1.091.726.138.882] 18-stack-info-depth
> [1.091.726.138.892] &"Cannot access memory at address 0x1b\n"
> [1.091.726.138.902] 18^error,msg="Cannot access memory at address 0x1b"
> [1.091.726.138.912] 18-stack-info-depth
> [1.091.726.138.932] (gdb)
> [1.091.726.139.323] &"Cannot access memory at address 0x1b\n"
> [1.091.726.139.323] 18^error,msg="Cannot access memory at address 0x1b"
> [1.091.726.139.333] (gdb)
>
> It seems to me looking for frames in the wrong direction? ;o)
> This causes a kind of error status, and the debugger is not able to step
> or watch something, but can continue or suspend.
>
> Also a known Problem?
>
> Ed
|
|
| | | |
Goto Forum:
Current Time: Sat May 24 07:43:20 EDT 2025
Powered by FUDForum. Page generated in 0.07954 seconds |
Home