| Another Eclipse 3.0 Debugger Problem [message #88435] |
Tue, 02 December 2003 13:26  |
Eclipse User |
|
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_009A_01C3B8CF.7CE5C580
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
When running the Eclipse 3 Debugger with CDST I am getting the following =
error:
ERROR: Launch : Failed Launching CDI Debugger
I am using the fully qualified path for the GDB Debugger =
(D:\Development\MinGW\bin\gdb.exe) and the is nothing in the GDB =
Command-line textbox. (There is no problem with this configuration in =
Eclipse 2.1)
Other Info:
WinXp Home Edition
512 ROM
Path=3DC:\WINDOWS\system32;..;C:\WINDOWS\system32\WBEM;C:\Ba t;C:\Program =
Files\Common Files\Adaptec =
Shared\System;C:\JAVA\j2sdk1.4.2_01\bin;C:\SqlLib\BIN;C:\Sql Lib\FUNCTION;=
D:\Development\VB6\Common\Tools\WinNT;D:\Development\VB6\Com mon\MSDev98\B=
in;D:\Development\VC98\bin;D:\Development\MinGW\bin
MinGW Version: #.1.0-1
CDT Version: 2.0M5
------=_NextPart_000_009A_01C3B8CF.7CE5C580
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1276" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>When running the Eclipse 3 Debugger =
with CDST I am=20
getting the following error:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><EM> ERROR: Launch : =
Failed=20
Launching CDI Debugger</EM></FONT></DIV>
<DIV><EM><FONT face=3DArial size=3D2></FONT></EM> </DIV>
<DIV><FONT face=3DArial size=3D2>I am using the fully qualified path for =
the GDB=20
Debugger (D:\Development\MinGW\bin\gdb.exe) and the is nothing in the =
GDB=20
Command-line textbox. (There is no problem with this configuration in =
Eclipse=20
2.1)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Other Info:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>WinXp Home Edition</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>512 ROM</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><FONT=20
size=3D2> Path=3DC:\WINDOWS\system32;..;C:\WINDOWS\system32\WBEM;C:\Ba t;C:=
\Program=20
Files\Common Files\Adaptec =20
Shared\System;C:\JAVA\j2sdk1.4.2_01\bin;C:\SqlLib\BIN;C:\Sql Lib\FUNCTION;=
D:\Development\VB6\Common\Tools\WinNT;D:\Development\VB6\Com mon\MSDev98\B=
in;D:\Development\VC98\bin;<STRONG>D:\Development\MinGW\bin </STRONG></FON=
T></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><FONT size=3D2>MinGW Version:=20
#.1.0-1</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>CDT Version: =
2.0M5</FONT></DIV></BODY></HTML>
------=_NextPart_000_009A_01C3B8CF.7CE5C580--
|
|
|
|
|
|
|
|
|
| Re: Eclipse 3.0 Debugger with CDT and gdb 5.2.1 [message #95124 is a reply to message #95109] |
Mon, 23 February 2004 21:08  |
| Eclipse User |
|
|
|
Originally posted by: holomorph.users.sourceforge.net
Yea, I suppose I could do that. Means I can't use the default path for
any projects, can't use "My Documents" etc. So as that will work I
thnik, it's really just avoiding the problem, not solving it.
Seeing as it works for other people (right?) I think there's something
funny with my system and I'd prefer to figure out what that is. Also,
since I can run my app in gdb in a cmd shell window, it might be
considered a bug in eclipse that it does not work to run it in there.
In that case, avoiding the problem is not helpful to anyone but me.
Bjorn
kesselhaus wrote:
> Well, why not just do the easiest thing at all?
> Just do not use directories with spaces within.
>
> .oO( Why do they just make things complicated? )
>
> bjorn wrote:
>
>> I've already got the newest version available from the Mingw website
>> (5.2.1).
>>
>> Mikhail Khodjaiants wrote:
>>
>>> Get the newer version of gdb.
>>>
>>> "bjorn" <holomorph@users.sourceforge.net> wrote in message
>>> news:c1e0p1$bo6$1@eclipse.org...
>>>
>>>> Yes, that is what is happening. I also discovered that things work in
>>>> eclipse if I use a directory path with no spaces for my project
>>>> directory. Any idea how I can fix this?
>>>>
>>>> Bjorn
>>>>
>>>> Mikhail Khodjaiants wrote:
>>>>
>>>>
>>>>> gdb returns this error when it tries to set the working directory. To
>>>
>>>
>>>
>>> verify
>>>
>>>>> this start gdb from the command line with "-i mi1" as an argument.
>>>>> Enter the following command:
>>>>> -environment-cd "C:\\Program Files\\eclipse\\workspace\\Hello".
>>>>>
>>>>> "Bjorn Hansen" <holomorph@users.sourceforge.net> wrote in message
>>>>> news:c13llo$b1v$1@eclipse.org...
>>>>>
>>>>>
>>>>>> Hi, I recently installed eclipse and the CTD plugin. I followed the
>>>>>> "hellow world" tutorial and everything worked fairly well until I
>>>>>> tried
>>>>>> to run the debugger. I got a popup with:
>>>>>> "ERROR: Launch : Failed Launching CDI Debugger".
>>>>>>
>>>>>> I opened the error log view to see if I could get more information
>>>>>> and
>>>>>> found it was getting this message:
>>>>>>
>>>>>> Unable to set working directory: "C:\\Program
>>>>>> Files\\eclipse\\workspace\\Hello": Invalid argument.
>>>>>>
>>>>>> The stack trace looks like:
>>>>>>
>>>>>> org.eclipse.cdt.debug.core.cdi.CDIException: Unable to set working
>>>>>> directory: "C:\\Program Files\\eclipse\\workspace\\Hello": Invalid
>>>>>
>>>>>
>>>>>
>>>>> argument.
>>>>>
>>>>>
>>>>>> at
>>>>>>
>>>>>
>>>>>
>>> org.eclipse.cdt.debug.mi.core.cdi.RuntimeOptions.setWorkingD irectory(Runtime
>>>
>>>
>>>>> Options.java:101)
>>>>>
>>>>>
>>>>>> at
>>>>>>
>>>>>
>>>>>
>>> org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDel egate.launch(Loc
>>>
>>>
>>>>> alCLaunchConfigurationDelegate.java:88)
>>>>>
>>>>>
>>>>>> at
>>>>>>
>>>>>
>>>>>
>>> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfigurati
>>>
>>>
>>>>> on.java:157)
>>>>>
>>>>>
>>>>>> at
>>>>>>
>>>>>
>>>>>
>>> org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlugin.jav
>>>
>>>
>>>>> a:778)
>>>>>
>>>>>
>>>>>> at
>>>
>>>
>>>
>>> org.eclipse.debug.ui.DebugUITools.buildAndLaunch(DebugUITool s.java:628)
>>>
>>>>>> at org.eclipse.debug.ui.DebugUITools$3.run(DebugUITools.java:58 4)
>>>>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:62)
>>>>>>
>>>>>> I can run the program from the command line, and run it in gdb as
>>>>>> well.
>>>>>> Any ideas why it's failing to set the working directory in eclipse?
>>>>>>
>>>>>> Bjorn
>>>>>>
>>>>>> in case it helps:
>>>>>> WindowsXP Home
>>>>>> CDT 2.0M6
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
|
|
|
|
| Re: Eclipse 3.0 Debugger with CDT and gdb 5.2.1 [message #95152 is a reply to message #95137] |
Tue, 24 February 2004 03:12 |
| Eclipse User |
|
|
|
bjorn wrote:
> Further experimentation reveals that running:
> gdb -i mi1
>
> and then typing:
> -environment-cd "C:\\Program Files\\eclipse\\workspace\\Hello"
>
> results in the error:
> &"\"C:\\\\Program Files\\\\eclipse\\\\workspace\": Invalid argument.\n"
> ^error,msg="\"C:\\\\Program Files\\\\eclipse\\\\workspace\": Invalid
> argument."
>
> but doing the same but leaving off the final closing quotation (or
> leaving out both quotation marks) works. So the problem appears to be
> that eclipse is enclosing the path string in quotes and gdb does not
> like that.
Sounds about par for the course. The totally idiotic idea to
*ALLOW* spaces in the path is the real problem. Even
Microsoft applications have problems some time!
I scrapped using spaces in file/directory names a long time
ago - after wasting two days fixing a Microsoft problem
resulting from the 'default directory' having a space in it
( Yes it was "Program Files" ;) )
--
Lester Caine
-----------------------------
L.S.Caine Electronic Services
|
|
|
Powered by
FUDForum. Page generated in 0.22993 seconds
Home