bug-glibc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: From Arasu (Digital India)


From: Andreas Jaeger
Subject: Re: From Arasu (Digital India)
Date: 07 Nov 2000 14:40:33 +0100
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Capitol Reef)

>>>>> B Ananda Arasu writes:

 > Hi,
 > I am Arasu working for Digital India. While porting from Sun Solaris to
 > Red Hat Linux 6.2 (for Intel computers), I faced some problems.

 > The 'C'  Programs gets compiled perfectly. But if  I run the program, it
 > gets strucked.
 > Then, I created debug image. Started debugging using 'gdb'. Again it gets
 > strucked. The stack contains the following data

 > #0  0x400d2ad4 in __libc_read () from /lib/libc.so.6
 > #1  0x4011c1ec in ?? () from /lib/libc.so.6
 > #2  0x40081951 in _IO_new_file_underflow (fp=0x4011a8c0) at fileops.c:385
 > #3  0x400838a1 in _IO_default_uflow (fp=0x4011a8c0) at genops.c:371
 > #4  0x40082d0c in __uflow (fp=0x4011a8c0) at genops.c:328
 > #5  0x40080066 in _IO_getc (fp=0x4011a8c0) at getc.c:39
 > #6  0x804e483 in yy_get_next_buffer () at lex.yy.c:2022
 > #7  0x804e23a in yylex () at lex.yy.c:1857
 > #8  0x8048fb6 in yyparse () at y.tab.c:985
 > #9  0x8048d38 in main (argc=5, argv=0xbffffc94)

 > I think it gets strucked in __libc_read() in /lib/libc.so.6. Actually it is
 > a standard C library.

 > I am using GNU Make 3.78.1, GCC 2.91.66 & GNU ld 2.9.5 .

 > Expecting your suggestions.
Fix your program ;-).

If it's stuck in libc_read, it's waiting for data - and that means
your program is somehow broken.  There're no known bugs in glibc in
this area.

Andreas
-- 
 Andreas Jaeger
  SuSE Labs address@hidden
   private address@hidden
    http://www.suse.de/~aj



reply via email to

[Prev in Thread] Current Thread [Next in Thread]