Re: other weird gdb-mi problems

[Miles Bader]

address@hidden (Nick Roberts) writes:
>  > p.s. What about emacs showing the wrong source file?
>
> which resets the frame.  The change below seems to fix this for the problem
> you reported with "up" and "down" by just specifying the thread,

Thanks, that patch fixes both problems for me.

BTW, a few other things I noticed while testing that:

 (1) Calling a program function from gdb to display various info; these
     no longer seems to work.

     E.g. if I do:  "call dump_loc(SOME_VAR)"
     where the "dump_loc" function just prints some stuff about SOME_VAR
     to stdout (and then flushes stdout).  In previous versions of gdb
     this worked great, but now it doesn't.

     This is actually kinda important, because it's a very commonly
     used technique to add gdb debugging hooks into programs...

     I thought maybe this had something to do with the
     "*input/output ...*" buffer which is now getting used, but the
     output didn't show up there either.


 (2) It display breakpoint icon in the margin, instead of in the
     fringe, if I have the "fringe-style" set to `half'.

     I guess maybe it's trying to ensure that the icon it fits in the
     space available, and indeed, there's like a single pixel chopped
     off one edge if I force it (by setting half-margin-mode _after_
     setting the breakpoint).

     However, having the margins are much more annoying than slightly
     truncated icons (especially since the icon is essentially, a red
     blob), so it would be nice if it were less eager about doing this,
     or tried to substitute a smaller icon in such a case, or something.

Thanks,

-Miles

-- 
"Suppose He doesn't give a shit?  Suppose there is a God but He
just doesn't give a shit?"  [George Carlin]