Issue Details (XML | Word | Printable)

Key: PCC-353
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Susi Lehtola
Votes: 1
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
pcc

Binaries compiled by PCC segfault in Fedora 15

Created: 27/May/11 10:52 AM   Updated: 01/Aug/11 09:52 AM
Component/s: None
Affects Version/s: None
Fix Version/s: None

File Attachments: 1. GZip Archive compile.log.gz (5 kB)
2. File objs.tar.bz2 (3 kB)



 Description  « Hide
Referring to
 https://bugzilla.redhat.com/show_bug.cgi?id=708305
binaries compiled by PCC do not work in Fedora 15 (glibc 2.13.90). PCC works fine in Fedora 14 (glibc-2.13).

Example: A Hello World program (a.c)

#include <stdio.h>
int main()
{
    printf("Hello\n");
    return 0;
}

compiled with
 $ pcc a.c
and run with
 $ ./a.out

results in
 Hello
in Fedora 14 x86_64, but
 $ ./a.out
 Segmentation fault (core dumped)
in Fedora 15.

Output of $valgrind ./a.out

==4974== Process terminating with default action of signal 11 (SIGSEGV)
==4974== Access not within mapped region at address 0x0
==4974== at 0x1: ???
==4974== by 0x40042D: __do_global_ctors_aux (in /tmp/a.out)
==4974== by 0x40034D: ??? (in /tmp/a.out)
==4974== by 0xE2: ???
==4974== by 0x400554: __libc_csu_init (in /tmp/a.out)
==4974== by 0x34892213CF: (below main) (libc-start.c:185)
==4974== If you believe this happened as a result of a stack
==4974== overflow in your program's main thread (unlikely but
==4974== possible), you can try to increase the size of the
==4974== main thread stack using the --main-stacksize= flag.
==4974== The main thread stack size used in this run was 8388608.


 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Susi Lehtola made changes - 11/Jul/11 11:21 AM
Field Original Value New Value
Attachment compile.log.gz [ 10209 ]
Susi Lehtola made changes - 01/Aug/11 09:52 AM
Attachment objs.tar.bz2 [ 10211 ]