Re: lisp/progmodes/gdb-ui.el

[Nick Roberts]

 > >  >...
 > >  > ^Z^Zpost-prompt
 > >  > Num Type           Disp Enb Address    What
 > >  > 1   breakpoint     keep y   0x080ba832 in rd_ch_unbuffered at 
 > > stream.d:5063
 > >  >         breakpoint already hit 1 time
 > >  > ") (recv . "
 > >  > ^Z^Zpre-prompt
 > >  > (gdb)
 > >  > ^Z^Zprompt
 > >  > ") ...)
 > >       ^^^
 > > 
 > > This ends in an ellipsis because the length of the list exceeds
 > > eval-expression-print-length. This means that you've not sent the start of
 > > the log.  Can you please make it unlimited by setting
 > > eval-expression-print-length to nil.
 > 
 > done

At the bottom of the log I see:

^Z^Zstarting

^Z^Zframes-invalid

^Z^Zframes-invalid

^Z^Zframes-invalid

^Z^Zsource 
/mnt/local/sda1/src/clisp/current/build-g/stream.d:5064:192834:beg:0x80ba83a

^Z^Zstopped
") (send-item "server info frame
" gdb-frame-handler) ...))


You have ^Z^Zstopped before ^Z^Zstarting (the log reads backwards) so it looks
like something is running the progran before you do.  But the log still ends in
ellipsis.  Maybe I'm wrong about eval-expression-print-length but I don't have
time to investigate.  Can you please find a way to get the full log?  (Maybe by
evaluating in the scratch buffer and clicking mouse-2 on the ellipsis.)


-- 
Nick                                           http://www.inet.net.nz/~nickrob