| A Tale of the Debugger [message #97519] |
Sat, 27 March 2004 04:29  |
Eclipse User |
|
|
|
Originally posted by: gw2.geneseo.edu
Hi Guys,
I just installed CDT with MinGW. I love it. Everything works except the
debugger. I'm just about to pull my hair out. =) I can make and execute
but I can't debug and here is the error returned from CDT:
Failed Launching CDI Debugger
Unable to set working directory: "C:\\Documents and
Settings\\Administrator\\My Documents\\Windows
Projects\\LanguageGenerator": Invalid argument.
I tried searched through the net, but nothing comes up.
I just want to know what the error means then I can solve it. Else, I'm
clueless. Could it be possible that the double \\ is causing problems?
Thanks in advance
Guang Yan
|
|
|
|
|
|
| Re: A Tale of the Debugger [message #97896 is a reply to message #97851] |
Sun, 28 March 2004 16:00  |
| Eclipse User |
|
|
|
Originally posted by: gw2.geneseo.edu
alain wrote:
> Guang Yan wrote:
> > > Probably the spaces
> > > put your workspace some place else.
> > Hmm, I don't think it is the workspace. I created another project with the
> > default workspace. I still get the same error.
> > Failed Launching CDI Debugger
> > Unable to set working directory: "C:Program
> > FileseclipseworkspaceLanguageGenerator": Invalid argument.
> C:Program Fileseclipseworkspace
> Seems to me that it still contains space in the path.
> > Where does that argument being supplied? Obviously to the mingw GDB. Where
> > probably should look something like c:GDB C:Program
> > FileseclipseworkspaceLanguageGeneratorgenerator.exe
> > I used the command promt and the debugger works. I have set the PATH
> > variable correctly. And the mingw32make works when I build the project.
> > The project runs when I press the run buttom. Why is GDB any different? I
> > think the argument supplied is wrong but I dunno where or how to change it?
> This is in the Debug launch, when the debugger is set to CygWinDebugger
> you will have a textfield allowing to set the starting working directory.
> This in turns maps it to a gdb command, something like
> -environ-cd C:Program Fileseclipse....
> For some reason, because of the space gdb throws an error.
> Putting double quotes will not help. Try setting to something else
> the project location i.e. something with no spaces.
> What version of gdb are you using?
> What version of CDT are you using?
> Start in debug mode, grab the gdb mi log output and make a PR
> out of it. Create a file containing :
> org.eclipse.cdt.debug.mi.core/debug=true
> start eclipse with -debug file:<path_of_the_file>
> > Thanks
Apparently the spaces within the path is bugging the debugger. I followed
your advise and made my default workspace in c:\\workspace which have no
spaces in the path, and the debugger worked. But the thing is, when I was
debugging in the command promt, I supplied the GDB with the full path that
contained spaces, and it worked fine.
I'm using the lastest build of minGW, the version of the GDB is GUN gdb
5.2.1
The version of CDT is 1.2.1
I'm still new to eclipse, so I'm not sure how to grab the gdb mi log
output
and make a PR out of it.
Do you think this is a bug with CDT?
Thank you so much for the help.
Guang Yan
|
|
|
| Re: A Tale of the Debugger [message #97909 is a reply to message #97896] |
Sun, 28 March 2004 20:19 |
| Eclipse User |
|
|
|
Originally posted by: alain.nowhere.ca
Guang Yan wrote:
> Apparently the spaces within the path is bugging the debugger. I followed
> your advise and made my default workspace in c:\workspace which have no
> spaces in the path, and the debugger worked. But the thing is, when I was
> debugging in the command promt, I supplied the GDB with the full path that
> contained spaces, and it worked fine.
You were not using the same mode at the prompt the mode CLI,
if you start gdb with the "-i mi" option, you would have the same problem.
Some the of MI commands do not parse arguments with space correctly.
Unfortunate.
> I'm using the lastest build of minGW, the version of the GDB is GUN gdb
> 5.2.1
> The version of CDT is 1.2.1
> I'm still new to eclipse, so I'm not sure how to grab the gdb mi log
> output
> and make a PR out of it.
> Do you think this is a bug with CDT?
The real fix would be to clean gdb mi mode ... Another battle.
|
|
|
Powered by
FUDForum. Page generated in 0.02810 seconds
Home