[core-updates-frozen] tcc fails to build

  • Done
  • quality assurance status badge
Details
2 participants
  • Robby Zambito
  • Guillaume Le Vaillant
Owner
unassigned
Submitted by
Guillaume Le Vaillant
Severity
normal
G
G
Guillaume Le Vaillant wrote on 27 Nov 2021 11:56
(address . bug-guix@gnu.org)
8735nhamm4.fsf@kitej
The 'check' phase fails with:

Toggle snippet (6 lines)
------------ test3 ------------
../tcc -B.. -I../include -I.. -I.. -DCONFIG_TCC_SYSINCLUDEPATHS="\"/gnu/store/2fk1gz2s7ppdicynscra9b19byrrr866-glibc-2.33/include:/gnu/store/99a2njzz22dkzd8pz75fsi5nbgv9ww0x-linux-libre-headers-5.10.35/include:{B}/include\"" -DCONFIG_TCC_LIBPATHS="\"/gnu/store/2fk1gz2s7ppdicynscra9b19byrrr866-glibc-2.33/lib\"" -DCONFIG_TCC_CRTPREFIX="\"/gnu/store/2fk1gz2s7ppdicynscra9b19byrrr866-glibc-2.33/lib\"" -DCONFIG_TCC_ELFINTERP="\"/gnu/store/2fk1gz2s7ppdicynscra9b19byrrr866-glibc-2.33/lib/ld-linux-x86-64.so.2\"" -DTCC_TARGET_X86_64 -run ../tcc.c -B.. -I../include -I.. -I.. -DCONFIG_TCC_SYSINCLUDEPATHS="\"/gnu/store/2fk1gz2s7ppdicynscra9b19byrrr866-glibc-2.33/include:/gnu/store/99a2njzz22dkzd8pz75fsi5nbgv9ww0x-linux-libre-headers-5.10.35/include:{B}/include\"" -DCONFIG_TCC_LIBPATHS="\"/gnu/store/2fk1gz2s7ppdicynscra9b19byrrr866-glibc-2.33/lib\"" -DCONFIG_TCC_CRTPREFIX="\"/gnu/store/2fk1gz2s7ppdicynscra9b19byrrr866-glibc-2.33/lib\"" -DCONFIG_TCC_ELFINTERP="\"/gnu/store/2fk1gz2s7ppdicynscra9b19byrrr866-glibc-2.33/lib/ld-linux-x86-64.so.2\"" -DTCC_TARGET_X86_64 -run ../tcc.c -B.. -I../include -I.. -I.. -DCONFIG_TCC_SYSINCLUDEPATHS="\"/gnu/store/2fk1gz2s7ppdicynscra9b19byrrr866-glibc-2.33/include:/gnu/store/99a2njzz22dkzd8pz75fsi5nbgv9ww0x-linux-libre-headers-5.10.35/include:{B}/include\"" -DCONFIG_TCC_LIBPATHS="\"/gnu/store/2fk1gz2s7ppdicynscra9b19byrrr866-glibc-2.33/lib\"" -DCONFIG_TCC_CRTPREFIX="\"/gnu/store/2fk1gz2s7ppdicynscra9b19byrrr866-glibc-2.33/lib\"" -DCONFIG_TCC_ELFINTERP="\"/gnu/store/2fk1gz2s7ppdicynscra9b19byrrr866-glibc-2.33/lib/ld-linux-x86-64.so.2\"" -DTCC_TARGET_X86_64 -run ../tcc.c -B.. -I../include -I.. -I.. -run tcctest.c > test.out3
make[1]: *** [Makefile:103: test3] Error 139
make[1]: Leaving directory '/tmp/guix-build-tcc-0.9.27.drv-0/tcc-0.9.27/tests'
make: *** [Makefile:347: test] Error 2
-----BEGIN PGP SIGNATURE-----

iIUEAREKAC0WIQTLxZxm7Ce5cXlAaz5r6CCK3yH+PwUCYaIQAw8cZ2x2QHBvc3Rl
by5uZXQACgkQa+ggit8h/j8z6wEAlY0eSb1Ws9BC+PNQiFbjm9f5beR8xSEl/3ZT
+TkWvtcBAKFkDzimKUuKmq7fOrG2wvg3o9y8xkZmvnIEdbcBcNfH
=u38Z
-----END PGP SIGNATURE-----

R
R
Robby Zambito wrote on 17 Dec 2021 05:26
(address . 52140@debbugs.gnu.org)(address . glv@posteo.net)
20211217042637.jfk433lhwgznmbyv@robby-Ryzen-RX-PC.localdomain
Hi,

I've noticed tcc seems to be failing for me on the current master branch
of guix (commit b2ae164b211f4da6a3cc5dcb97eeeff3c6c7ebed according to
guix describe).

I tried to see if I could debug the issue, but I've reached the limit of
my knowledge.

The issue occurs on line 168 of tcc_run.c. That function call that is
executed seems to overwrite the memory of s1, which is a struct that
includes a FILE*. Because that FILE* is changed, the later call to
fclose(ppfp) on line 369 of tcc.c causes a segfault, because it no
longer points to a valid FILE.

I have no idea how to start debugging the function call at line 168 of
tcc_run.c, since that is code that has actually been compiled by tcc,
rather than tcc itself (though obviously code that is a part of the test
suite).

I hope we can get this working again.

Thanks,
Robby
G
G
Guillaume Le Vaillant wrote on 5 Sep 2022 14:33
Re: bug#52140: [core-updates-frozen] tcc fails to build
(address . 52140-close@debbugs.gnu.org)
87pmga9ez7.fsf@kitej
tcc currently builds successfully.
Closing.
-----BEGIN PGP SIGNATURE-----

iIUEAREKAC0WIQTLxZxm7Ce5cXlAaz5r6CCK3yH+PwUCYxXs7A8cZ2x2QHBvc3Rl
by5uZXQACgkQa+ggit8h/j9RkAD8DpyLDqfJfr0UybJZ4GwwPXiuVqtunzRN+K56
gpwozLcA/jHjQxCoVms0eRmTvZBn3vgZWcG3Vuhr+KNAbNJMxVui
=OYzn
-----END PGP SIGNATURE-----

?
Your comment

This issue is archived.

To comment on this conversation send an email to 52140@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 52140
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch