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

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

[Kefei Lu]

Hi support,

I can't do "next" or "step" in insight. When I press the button, the
green highlighted line stays where it was. So I opened a gdb console
in insight and type "n", this time it showed:

(gdb) n
Error: Warning:
Cannot insert breakpoint -11.
Error accessing memory address 0x29be0: Input/output error.

I reinstalled insight and gdb, and the problem remained.

I'm using Ubuntu 7.04, GNU gdb 6.6-debian, but "insight --version"
shows "GNU gdb 6.5".

Thanks a lot!

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

[Keith Seitz]

Kefei Lu wrote:

> (gdb) n
> Error: Warning:
> Cannot insert breakpoint -11.
> Error accessing memory address 0x29be0: Input/output error.

If gdb itself is not able to step the target, you're best bet is to 
bring this up on the gdb mailing list (gdb@). Insight is really just a 
GUI and a bunch of glue code to gdb. This is definitely a problem w/gdb 
proper, so you are likely to get much better information from the gdb 
community than I can offer.

Keith

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

[Kefei Lu]

Hi Keith,

Thanks for reply.

Yes, my gdb works fine.

As I said, ``gdb --version'' and ``insight --version'' gives different
version number on gdb. So I guess insight wrapped its own version of
gdb, which might be broken.

But how can I invoke and test that version of gdb without invoking
insight to check the problem?

On Sun, May 4, 2008 at 8:07 PM, Keith Seitz <keiths@redhat.com> wrote:
> Kefei Lu wrote:
>
>
> > (gdb) n
> > Error: Warning:
> > Cannot insert breakpoint -11.
> > Error accessing memory address 0x29be0: Input/output error.
> >
>
>  If gdb itself is not able to step the target, you're best bet is to bring
> this up on the gdb mailing list (gdb@). Insight is really just a GUI and a
> bunch of glue code to gdb. This is definitely a problem w/gdb proper, so you
> are likely to get much better information from the gdb community than I can
> offer.
>
>  Keith
>



-- 
Sincerely,
Kefei Lu

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

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

[Keith Seitz]

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

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

[Kefei Lu]

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.

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

[Keith Seitz]

Kefei Lu wrote:
> klu@klu-lab:~/work/blahut/examples$ insight --i=console ucBsc.out
> GNU gdb 6.5
   ^^^^^^^^^^^

6.5 was released on June 26, 2006. I would highly recommend you try 
something a bit newer (6.7.1 or even a snapshot).

Keith

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

[Kefei Lu]

This version of insight was installed from Ubuntu repository. Maybe I
need to build one by myself:)))

Thanks for your help!

On Mon, May 5, 2008 at 12:04 PM, Keith Seitz <keiths@redhat.com> wrote:
> Kefei Lu wrote:
>
> > 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? :(
> >
>
>  Two points. First, the session you posted is perfect. That is exactly what
> GDB folk are going to need to see. Second, You're using gdb 6.6, but you
> insight is based on 6.5 -- which is VERY old. At the very least,  download
> and build the insight 6.6 tarball (or a newer one -- current release is
> 6.7.1). I'm not surprised to hear that a gdb of that vintage is having
> problems: there was a lot of churn in thread libraries and a bunch of gdb
> subsystems around that time.
>
>  Keith
>



-- 
Sincerely,
Kefei Lu

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