Date: Wed, 2 Sep 2009 12:33:26 GMT From: gonebsd <gonebsd@gmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/138481: lang/tcc: tcc compiled executables segfault Message-ID: <200909021233.n82CXQl1081093@www.freebsd.org> Resent-Message-ID: <200909021240.n82Ce6gV045573@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 138481
>Category: ports
>Synopsis: lang/tcc: tcc compiled executables segfault
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Sep 02 12:40:06 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator: gonebsd
>Release: FreeBSD 7.2-RELEASE-p3 i386
>Organization:
>Environment:
>Description:
Every executable compiled using tcc segfaults. Interestingly,
if the "-run" is used, the program executes as expected. See
the "how to repeat the problem" below.
I tried tcc version 0.9.24 (via pkg_add) and 0.9.25 (via ports,
using gcc 4.2.1) with the same results.
This seems to be FreeBSD specific since I cannot reproduce this
on Linux (Arch, with gcc 4.4.1) at all.
>How-To-Repeat:
echo 'main(){puts("hello");}' | tcc -o output - && ./output
Segmentation fault (core dumped)
And with "-run":
echo 'main(){puts("hello");}' | tcc -run -
hello
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200909021233.n82CXQl1081093>