ddbg_gdb with emacs
Jascha Wetzel
"[firstname]" at mainia.de
Tue Feb 27 12:11:40 PST 2007
ah, ic!
the missing filename isn't an output format issue. C::B requires the
full pathname, so i try to find it using the source search paths that
have been set with the "directory" command. if ddbg can't find the
absolute path, it doesn't output any filename - that's going to be fixed
in the next release.
hm, all these different GDB output formats are pretty annoying. any
chance to make emacs work with GDB/MI (Machine Interface)?
Bill Baxter wrote:
> Here's some additional info I've found.
>
> You probably already realized this, but this output
> " C:/tmp/mingwdbg/hello.c:22:496:beg:0x401322"
> is also generated with the --fullname, which you're already supporting
> (actually you're generating --fullname output whether or not the flag is
> supplied :-P)
>
> So I'm not sure why it doesn't already work. The only difference I can
> see is that you omit the filename.
> " :22:496:beg:0x401322"
>
> and maybe emacs needs that filename there.
>
> Can you try just adding the full filename to that output string?
>
> That should enable emacs to at least display the current source line.
>
>
> Unfortunately I discovered there's another file called gdb-ui.el that
> implements most of the other nifty features of the gdb mode, like
> showing breakpoints etc. It is triggered by finding "\n prompt" in the
> output after "(gdb)" which is something --annotate prints.
>
> The extended processing relies pretty heavily on the specific format of
> --annotate=3 output.
> Here's a url for gdb-ui.el for the record: http://tinyurl.com/25b6gw
> Specifically the thing to look for is the function
> (defun gud-gdba-marker-filter ... )
>
>
>
> --bb
More information about the Digitalmars-d-debugger
mailing list