Re: GSoC gdb-mi.el changes

[Dmitry Dzhus]

Dan Nicolaescu wrote:

> Suggestion: don't show the -i=mi flag, users don't care about it (same
> way rgrep/lgrep don't show the -n flag they pass to grep)

I'll do this.

> Issues:
> echo 'int main () { printf ("Hello, World!\n");}' > t.c
> gcc t.c
> emacs -Q 
> M-x gdb RET ./a.out RET
>
> error in process filter: Symbol's function definition is void: mapcar*
>
> M-x load-library RET cl RET
> M-x gdb RET ./a.out RET

Uh-oh, that's very bad. Somehow I thought that mapcar* is a macro. I'll
rewrite some of my functions without mapcar* then.

>
> Show the disassembly window
>
> b main
>
> A warning pops up:
> &"warning: GDB: Failed to set controlling terminal: Operation not permitted\n"
>
> si 
> si 
> si
>
> The cursor in the disassembly does not move correctly when single
> stepping and it does not update the stack frames all the time.

(At the time of your writing, stepping was just broken; I installed some
fixes in CVS.)

Does it occur when you compile your target with -g, too?

Unlike GDB's CLI `disassemble` command, to show disassembly code for you
program, MI needs to know either file:line information for the function
you're interested in, or its memory range. For the former your target
needs to be compiled with debugging information, and for the latter we
need to query GDB for function memory range, but this command is not
implemented in GDB/MI yet :(
-- 
Happy Hacking.

http://sphinx.net.ru
む