- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I am having trouble following the debugger documentation to invoke the idb(V10) debugger from within emacs 22 (on windowsXP+cygwin)
My procedure is to load the source file, and invoke gdb. I am then prompted as follows:
Run gdb (like this):
To which I reply:
C:Program FilesIntelIDB10.0IA32inidb -gdb -fullname mycode.exe
Emacs complains about spawning child process: invalid argument. I think the problem lies in the space in "Program Files". I tried various combinations of backward slashes, quotes, etc, but no success.
Many thanks,
Mirko
I am having trouble following the debugger documentation to invoke the idb(V10) debugger from within emacs 22 (on windowsXP+cygwin)
My procedure is to load the source file, and invoke gdb. I am then prompted as follows:
Run gdb (like this):
To which I reply:
C:Program FilesIntelIDB10.0IA32inidb -gdb -fullname mycode.exe
Emacs complains about spawning child process: invalid argument. I think the problem lies in the space in "Program Files". I tried various combinations of backward slashes, quotes, etc, but no success.
Many thanks,
Mirko
Link Copied
4 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Emacs in the cygwin environment will spawn via the cygwin libraries. My recommendations is to try the "unix path" version of the IDB. Type
cygpath --unix "C:Program FilesIntelIDB10.0IA32binidb"
Note the to escape the
Use the translated path instead and see if that works.
The other part of the equation is that idb will expect a Windows style name. Thus, the argument you pass to idb as the file name needs to be something that idb understands.
cygpath --unix "C:Program FilesIntelIDB10.0IA32binidb"
Note the to escape the
Use the translated path instead and see if that works.
The other part of the equation is that idb will expect a Windows style name. Thus, the argument you pass to idb as the file name needs to be something that idb understands.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
James,
I was not clear enough in my post (too many installed components on my computer) . I am using the windows version of emacs (downloaded from the gnu web site)
I asked the question on gnu.emacs.help, and got an answer that got me somewhere. I should invoke idb with:
c:progra~1intel...
(that may need to go as a correction for the documentation)
Now the debugger works. The display in emacs is not quite right, but the interaction with the debugger seems to work.
Thanks,
Mirko
I was not clear enough in my post (too many installed components on my computer) . I am using the windows version of emacs (downloaded from the gnu web site)
I asked the question on gnu.emacs.help, and got an answer that got me somewhere. I should invoke idb with:
c:progra~1intel...
(that may need to go as a correction for the documentation)
Now the debugger works. The display in emacs is not quite right, but the interaction with the debugger seems to work.
Thanks,
Mirko
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As a follow up on this thread, there is a resolution for this issue.
Nick Roberts posted a patch for gud.el on gnu.emacs.help. You can find it on this thread:
how to start the intel debugger with dgb in emacs
It basically consists of calling string->strings instead of string-strings. His post contains the definition of string->strings function.
At the same time, I learned the intel is dropping idb development after this release. So the issue may be moot :-(
Mirko
Nick Roberts posted a patch for gud.el on gnu.emacs.help. You can find it on this thread:
how to start the intel debugger with dgb in emacs
It basically consists of calling string->strings instead of string-strings. His post contains the definition of string->strings function.
At the same time, I learned the intel is dropping idb development after this release. So the issue may be moot :-(
Mirko
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just to clarify - we will no longer be developing idb for Windows. idb for Linux and MacOS will still be there. Windows users seem to universally prefer the MS debugger, though I can understand why you might want to use idb from Cygwin.
It's not going away for a while yet, though.
It's not going away for a while yet, though.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page