[Top][All Lists]

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

Re: [Tinycc-devel] Segmentation fault in tccelf.c:2189, strcmp

From: Evan Langlois
Subject: Re: [Tinycc-devel] Segmentation fault in tccelf.c:2189, strcmp
Date: Wed, 26 Oct 2005 22:42:08 -0500

On Tue, 2005-10-25 at 21:25 -0400, Diego Bauche Madero wrote:

> As you can see, `name' points to the address i said, and of course, being not 
> an accesable address, the program just sends SIGSEGV.
> Anyway, the core file and tcc ELF executable binary (compiled with glibc 
> 2.3.4) can be found at http://genexx.org/tcc_strcmp.tbz2

The question isn't if name is that address or not, the question is why
isn't that address within the application's memory map.

> $ tcc -IGL /usr/X11R6/lib/libX11.so.6 /usr/X11R6/lib/libXext.so.6
> /usr/X11R6/lib/libGLU.so /usr/X11R6/lib/libglut.so.3 -lGL -IGLU -lm -o
> libellenbeck-fract libellenbeck-fract.c
> Segmentation fault
> $ gcc -IGL /usr/X11R6/lib/libX11.so.6 /usr/X11R6/lib/libXext.so.6
> /usr/X11R6/lib/libGLU.so /usr/X11R6/lib/libglut.so.3 -lGL -IGLU -lm -o
> libellenbeck-fract libellenbeck-fract.c

Well, it would seem to be a bug.  However, rogue pointers can cause
really odd problems that may work on some systems and not others, or may
only show on certain compilation or optimization options, etc.

Can you narrow down the issue into a smaller test case, preferably
without all the library dependancies?  Is the source available?  Its
usually easier to look at the source than trying to look through a core

-- Evan

reply via email to

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