Re: [Problem] I can't do "next" in insight!

["Kefei Lu" <lukefei@gmail.com>]

Thanks for the help! I've tried in console mode and the log file is
post as following. I'll also post this mail at gdb's mailing list.
Just feel strange why insight suddenly broke and why my gdb 6.6 is
still working. What I've done? :(

========================
klu@klu-lab:~/work/blahut/examples$ insight --i=console ucBsc.out
GNU gdb 6.5
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db
library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) b main
Breakpoint 1 at 0x8048bce: file examples/ucBsc.c, line 12.
(gdb) r
Starting program: /home/klu/work/blahut/examples/ucBsc.out
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
Error while mapping shared library sections:
/lib/tls/i686/cmov/libm.so.6: No such file or directory.
Error while mapping shared library sections:
/usr/lib/libgsl.so.0: No such file or directory.
Error while mapping shared library sections:
/usr/lib/libgslcblas.so.0: No such file or directory.
Error while mapping shared library sections:
/lib/tls/i686/cmov/libc.so.6: No such file or directory.
Error while mapping shared library sections:
/lib/ld-linux.so.2: No such file or directory.

Breakpoint 1, main (argc=1, argv=0xbfbcbab4) at examples/ucBsc.c:12
warning: Source file is more recent than executable.
12          if (argc > 2) {
(gdb) n

On Mon, May 5, 2008 at 11:41 AM, Keith Seitz <keiths@redhat.com> wrote:
> Kefei Lu wrote:
>
>
> > But how can I invoke and test that version of gdb without invoking
> > insight to check the problem?
> >
>
>  You can invoke insight with the command line option "--i=console". That
> should get you back to "normal" gdb.
>
>  Keith
>



-- 
Sincerely,
Kefei Lu

------------------------
Kefei Lu, Ph.D. candidate
Dept. of Electrical and Computer Engineering
Univ. of Miami, U.S.A.