tinycc-devel
[Top][All Lists]
Advanced

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

Re: [Tinycc-devel] TCC segfault on Fedora 29


From: Michael Matz
Subject: Re: [Tinycc-devel] TCC segfault on Fedora 29
Date: Mon, 4 Mar 2019 17:47:50 +0000 (UTC)
User-agent: Alpine 2.21 (LSU 202 2017-01-01)

Hi,

On Mon, 4 Mar 2019, Christian Jullien wrote:

> Ooops, not quite.
> I missed this line on log file (from Fedora 29).
> Btw, as suggested by ./configure,  Fedora 29 requires --with-selinux
> 
> ------------ dlltest ------------
> ../tcc -B.. -I../include -I.. -I.. -DCONFIG_LDDIR="\"lib64\""
> -DTCC_TARGET_X86_64 -DHAVE_SELINUX -DLIBTCC_AS_DLL ../libtcc.c -lm -ldl
> -shared -o libtcc2.so
> make[1]: *** [Makefile:132: dlltest] Segmentation fault (core dumped)

Different bug?  I don't have fedora 29 so can't debug this myself, what 
does the gdb backtrace look like for the coredump (to make that easier, 
build tcc with '-O0 -g', not the default -O2, i.e. change CFLAGS in 
config.mak).


Ciao,
Michael.


> 
> -----Original Message-----
> From: Tinycc-devel [mailto:address@hidden
> On Behalf Of Michael Matz
> Sent: lundi 4 mars 2019 16:58
> To: address@hidden
> Subject: Re: [Tinycc-devel] TCC segfault on Fedora 29
> 
> Hi,
> 
> On Fri, 1 Mar 2019, Klaus Ebbe Grue wrote:
> 
> > Is there news on the Fedora 29 segfault problem?
> 
> No, as nobody provided the breaking crt*.o files ...
> 
> > > some time. Alternatively: somebody can send me their /usr/lib64/crt*.o
> > > files from a system where the segfault reproduces. It's some unhandled
> > 
> > I have included my /usr/lib64/crt*.o files, if that helps (I hope the 
> > mailing list accepts attachments).
> 
> ... until now.  Fixed in mob.
> 
> 
> Ciao,
> Michael.
> 
> _______________________________________________
> Tinycc-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/tinycc-devel
> 
> 
> _______________________________________________
> Tinycc-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/tinycc-devel
> 



reply via email to

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