Home » Language IDEs » C / C++ IDE (CDT) » Debugging with Cygwin GDB
| Debugging with Cygwin GDB [message #46014] |
Mon, 21 October 2002 07:58  |
Eclipse User |
|
|
|
Originally posted by: ijmuiden.pointbreak.biz
I'm having a problem using the CDT integrated debugging features under
Windows/Cygwin. Instead of getting a debugging perspective, I get the
standard user interface of the gdb debugger, since under Cygwin, gdb is
installed to launch a user interface (instead of running in console mode) by
default. This can be turned of by using the -nw option, but Eclipse doesn't
seem to use that option, and I can not find a dialog/window in Eclipse to
make it use that option.
Consequently, Eclipse gives me a timeout when starting the debugger (can not
set initial breakpoints), since it can not communicate with the user
interface, and I find the following in the log files:
!ENTRY org.eclipse.cdt.debug.core 4 5010 okt 21, 2002 13:43:47.898
!MESSAGE org.eclipse.cdt.debug.core.cdi.CDIException:
org.eclipse.cdt.debug.mi.core.MIException: Timedout occurred setting
temporary breakpoint.
!STACK 0
org.eclipse.cdt.debug.core.cdi.CDIException:
org.eclipse.cdt.debug.mi.core.MIException: Timedout
at
org.eclipse.cdt.debug.mi.core.cdi.BreakpointManager.setLocat ionBreakpoint(Br
eakpointManager.java:293)
at
org.eclipse.cdt.debug.core.CDebugModel.newDebugTarget(CDebug Model.java:115)
at
org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDel egate.launch(Loc
alCLaunchConfigurationDelegate.java:118)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfigurati
on.java:136)
at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchCon figurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext
..java:98)
Is there anybody who knows how to make Eclipse bypass the user interface of
gdb? Any help is appreciated.
Gerjon
|
|
|
| Re: Debugging with Cygwin GDB [message #46044 is a reply to message #46014] |
Mon, 21 October 2002 10:45  |
| Eclipse User |
|
|
|
Your situation is very strange. Try to look at
org.eclipse.cdt.debug.mi.core.MIPlugin.java. If you find CreateCSession
function there you can see string looks approximately like
args = new String[] {gdb, "-q", "-nw", "-tty", pty.getSlaveName(), "-i",
"mi1", program};
or like
args = new String[] {gdb, "-q", "-nw", "-i", "mi1", program};
As we can see options of gdb starting define in this strings. Try to
change it somehow.
Hope it help,
Igor S. Zamyatin
Interstron Ltd.
----------------------------------------
email: isz@interstron.ru
tel: +7 (095) 269-4713
cell: +7 (902) 659-5838
www: http://www.interstron.ru
Gerjon wrote:
> I'm having a problem using the CDT integrated debugging features under
> Windows/Cygwin. Instead of getting a debugging perspective, I get the
> standard user interface of the gdb debugger, since under Cygwin, gdb is
> installed to launch a user interface (instead of running in console mode) by
> default. This can be turned of by using the -nw option, but Eclipse doesn't
> seem to use that option, and I can not find a dialog/window in Eclipse to
> make it use that option.
> Consequently, Eclipse gives me a timeout when starting the debugger (can not
> set initial breakpoints), since it can not communicate with the user
> interface, and I find the following in the log files:
> !ENTRY org.eclipse.cdt.debug.core 4 5010 okt 21, 2002 13:43:47.898
> !MESSAGE org.eclipse.cdt.debug.core.cdi.CDIException:
> org.eclipse.cdt.debug.mi.core.MIException: Timedout occurred setting
> temporary breakpoint.
> !STACK 0
> org.eclipse.cdt.debug.core.cdi.CDIException:
> org.eclipse.cdt.debug.mi.core.MIException: Timedout
> at
> org.eclipse.cdt.debug.mi.core.cdi.BreakpointManager.setLocat ionBreakpoint(Br
> eakpointManager.java:293)
> at
> org.eclipse.cdt.debug.core.CDebugModel.newDebugTarget(CDebug Model.java:115)
> at
> org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDel egate.launch(Loc
> alCLaunchConfigurationDelegate.java:118)
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfigurati
> on.java:136)
> at
> org.eclipse.debug.internal.ui.launchConfigurations.LaunchCon figurationDialog
> $10.run(LaunchConfigurationDialog.java:2299)
> at
> org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext
> ..java:98)
> Is there anybody who knows how to make Eclipse bypass the user interface of
> gdb? Any help is appreciated.
> Gerjon
|
|
|
| Re: Debugging with Cygwin GDB [message #46375 is a reply to message #46044] |
Tue, 22 October 2002 12:32 |
| Eclipse User |
|
|
|
Originally posted by: ijmuiden.pointbreak.biz
Thanks for your response. I see that the version of CDT I'm using does not
use the "-nw" parameter; I'll update.
"Igor S. Zamyatin" <isz@interstron.ru> schreef in bericht
news:ap13uo$u9p$1@rogue.oti.com...
>
>
> Your situation is very strange. Try to look at
> org.eclipse.cdt.debug.mi.core.MIPlugin.java. If you find CreateCSession
> function there you can see string looks approximately like
>
> args = new String[] {gdb, "-q", "-nw", "-tty", pty.getSlaveName(), "-i",
> "mi1", program};
>
> or like
>
> args = new String[] {gdb, "-q", "-nw", "-i", "mi1", program};
>
> As we can see options of gdb starting define in this strings. Try to
> change it somehow.
>
>
> Hope it help,
> Igor S. Zamyatin
> Interstron Ltd.
> ----------------------------------------
> email: isz@interstron.ru
> tel: +7 (095) 269-4713
> cell: +7 (902) 659-5838
> www: http://www.interstron.ru
>
>
>
>
> Gerjon wrote:
>
> > I'm having a problem using the CDT integrated debugging features under
> > Windows/Cygwin. Instead of getting a debugging perspective, I get the
> > standard user interface of the gdb debugger, since under Cygwin, gdb is
> > installed to launch a user interface (instead of running in console
mode) by
> > default. This can be turned of by using the -nw option, but Eclipse
doesn't
> > seem to use that option, and I can not find a dialog/window in Eclipse
to
> > make it use that option.
>
> > Consequently, Eclipse gives me a timeout when starting the debugger (can
not
> > set initial breakpoints), since it can not communicate with the user
> > interface, and I find the following in the log files:
> > !ENTRY org.eclipse.cdt.debug.core 4 5010 okt 21, 2002 13:43:47.898
>
> > !MESSAGE org.eclipse.cdt.debug.core.cdi.CDIException:
> > org.eclipse.cdt.debug.mi.core.MIException: Timedout occurred setting
> > temporary breakpoint.
>
> > !STACK 0
>
> > org.eclipse.cdt.debug.core.cdi.CDIException:
> > org.eclipse.cdt.debug.mi.core.MIException: Timedout
>
> > at
> >
org.eclipse.cdt.debug.mi.core.cdi.BreakpointManager.setLocat ionBreakpoint(Br
> > eakpointManager.java:293)
>
> > at
> >
org.eclipse.cdt.debug.core.CDebugModel.newDebugTarget(CDebug Model.java:115)
>
> > at
> >
org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDel egate.launch(Loc
> > alCLaunchConfigurationDelegate.java:118)
>
> > at
> >
org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfigurati
> > on.java:136)
>
> > at
> >
org.eclipse.debug.internal.ui.launchConfigurations.LaunchCon figurationDialog
> > $10.run(LaunchConfigurationDialog.java:2299)
>
> > at
> >
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext
> > ..java:98)
>
>
>
> > Is there anybody who knows how to make Eclipse bypass the user interface
of
> > gdb? Any help is appreciated.
>
>
>
> > Gerjon
>
>
>
>
>
>
>
>
>
>
|
|
|
Goto Forum:
Current Time: Fri May 09 18:00:29 EDT 2025
Powered by FUDForum. Page generated in 0.02682 seconds |
Home