This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Bug report


This works on the same machine with gcc 2.7.2.3 and on another machine with gcc 2.91.66.
This was actually out of an autoconf script.
 don't know if this will be helpful, the gdb backtrace

 on the core file
(gdb) bt
#0  0x40076262 in strrchr ()
#1  0xbffff594 in ?? ()
#2  0x40030cb3 in __libc_start_main (main=0x80483f0 <main>, argc=1, argv=0xbffff594, 
    init=0x804829c <_init>, fini=0x8048444 <_fini>, rtld_fini=0x4000a350 <_dl_fini>, 
    stack_end=0xbffff58c) at ../sysdeps/generic/libc-start.c:78
(gdb) quit


#line 2039 "configure"
/* System header to define __stub macros and hopefully few prototypes,
    which can conflict with char strrchr(); below.  */
#include <assert.h>
/* Override any gcc2 internal prototype to avoid an error.  */
/* We use char because int might match the return type of a gcc2
    builtin and then its argument prototype would still apply.  */
char strrchr();

int main() {

/* The GNU C library defines this for functions which it implements
    to always fail with ENOSYS.  Some functions are actually named
    something starting with __ and the normal name is an alias.  */
#if defined (__stub_strrchr) || defined (__stub___strrchr)
choke me
#else
strrchr();
#endif

; return 0; }


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]