Can't read(0,buf,1) in gdb-4.7

Thread View: gnu.gdb.bug

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Richard W. Kreutzer Consultant Wed, 28 Oct 1992 22:29

#22

Author: Richard W. Kreutzer Consultant
Date: Wed, 28 Oct 1992 22:29

26 lines
1052 bytes

When I do the following:

main() {
  char a[1];
  read(0, a, 1);
  }

gcc -o main main.c
gdb main
> r
Program received signal 21, Stopped (tty input)
0xf77371c4 in read ()

I get the above error message.  This worked for me in 4.5 and 4.6.  I am using
gcc-2.2.2 but the problem occurs with cc as well (with or without -g).  I am
running SunOS 4.1.1 on a SPARCstation 1+.

Is this a bug of have I compiled gdb wrong?

Also, I am unable to get "cfront" name demangling to work with Sun CC v2.1.
Do you believe it works with cfront-2.1 on a Sun?


Thanks,

Dick

Re: Can't read(0,buf,1) in gdb-4.7

#33

Author: gnu
Date: Sat, 31 Oct 1992 08:29

12 lines
998 bytes

We can't reproduce this problem.  My guess is that you compiled gdb with
gcc, without running "fixincludes".  Run fixincludes in the gcc
directory, make clean in the gdb-4.7 directory, and remake gdb.

> Also, I am unable to get "cfront" name demangling to work with Sun CC v2.1.
> Do you believe it works with cfront-2.1 on a Sun?

We have no belief about cfront-2.1 on the Sun.  We don't have it and
haven't tested it.  The improvements we've made in cfront demangling were
done on an NCR 486 box.

	John

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads