building gdb ...

building gdb ...

[Mark Pilon]

I received a patch to fix the problem of gdb core dumping while
debugging a kernel ... and have hit a snag:

after I built gdb 5.0, right from the gnu distribution,
I ran it -- got the gdb header and prompt and then nothing.

-- it's as if it's not checking stdin or stdin has been redirected
elsewhere ...

I debug'd gdb and got to:

-- (gdb)
Continuing.

Program received signal SIGINT, Interrupt.
0x40129f50 in __poll (fds=0x81c8e30, nfds=1, timeout=-1)
    at ../sysdeps/unix/sysv/linux/poll.c:45
45      in ../sysdeps/unix/sysv/linux/poll.c
(gdb) where
#0  0x40129f50 in __poll (fds=0x81c8e30, nfds=1, timeout=-1)
    at ../sysdeps/unix/sysv/linux/poll.c:45
#1  0x80c9502 in gdb_wait_for_event () at event-loop.c:773
#2  0x80c8fd2 in gdb_do_one_event (data=0x0) at event-loop.c:408
#3  0x80b2183 in catch_errors (func=0x80c8fbc <gdb_do_one_event>, args=0x0,
    errstring=0x816e480 "", mask=6) at top.c:615
#4  0x80c9003 in start_event_loop () at event-loop.c:438
#5  0x8091705 in cli_command_loop () at event-top.c:196
#6  0x806a675 in captured_command_loop (data=0x0) at main.c:104
#7  0x80b2183 in catch_errors (func=0x806a660 <captured_command_loop>,
    args=0x0, errstring=0x8145f11 "", mask=6) at top.c:615
#8  0x806b053 in captured_main (data=0xbffff9b0) at main.c:749
#9  0x80b2183 in catch_errors (func=0x806a6a4 <captured_main>,
    args=0xbffff9b0, errstring=0x8145f11 "", mask=6) at top.c:615
#10 0x806b07f in main (argc=1, argv=0xbffffa04) at main.c:761
(gdb) p *fds
$3 = {fd = 0, events = 1, revents = 0}
(gdb) quit

-- the call to poll appears to be looking for input on fd 0 ...
but stdin isn't consumed by this gdb.  if I suspend, all the
keystrokes I typed @ the gdb prompt then appear as if passed to
the shell.

did I miss something in the configure line? my configure line:
   ./configure --target=powerpc-linux \
      --host=i586-pc-linux-gnu \
      --prefix=/home/mpilon/ppc_tools/ppc_home

has anyone seen this?

Mark
Mark Pilon

Minolta-QMS
P.O. Box 37
Fallon, MT.  59326-0037

1-406-853-0433

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: building gdb ... no input

[Mark Pilon]

one more data point ... I copied the .tar.gz archive of gdb5.0
to a vanilla redhat 6.2 machine, did the same configure, built
a gdb and it does respond to keyboard input ...?

I've diff'd gdb/config.h between the 2 builds and there's no
difference.  any idea what else I can check for differences?

Mark

--
Mark Pilon

Minolta-QMS
P.O. Box 37
Fallon, MT.  59326-0037

1-406-853-0433

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: building gdb ... no input

[Mark Pilon]

I've traced the problem as far as configuring w/ --prefix= pointing
to my ppc tools & glibc home, wanting the tools to be installed
w/ gcc et al.

I haven't debugged it all the way, but the build of readline was
complaining of ambiguous endian-ness because it was picking endian.h
from my ppc include dir ...

So.  I'll build w/o specifying a --prefix dir, and make install
specifying an install_root ...

Time to watch the Simpsons ... Doh!

Mark

--
Mark Pilon

Minolta-QMS
P.O. Box 37
Fallon, MT.  59326-0037

1-406-853-0433

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/