[Bug 3505] New: gcc -static compilation has exit() call _stdio_term which is null
bugzilla at busybox.net
bugzilla at busybox.net
Thu Mar 24 12:42:44 UTC 2011
https://bugs.busybox.net/show_bug.cgi?id=3505
Summary: gcc -static compilation has exit() call _stdio_term
which is null
Product: uClibc
Version: 0.9.30.2
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at uclibc.org
ReportedBy: paul.barbieri at baesystems.com
CC: uclibc-cvs at uclibc.org
Estimated Hours: 0.0
I have applied the gcc PR32219 patches which use not_null_ptr() when testing
existence of _stdio_init, _locale_init, __errno_location, and
__h_errno_location. This gets me past __uClibc_init but now I die in _atexit.c:
exit() routine which calls _stdio_term. I have put the same not_null_ptr()
functionality in and the problem goes away but I did not see any changes in the
current upstream to deal with this same issue.
My test program is foo.c compiled and linked as shown below:
int main(int argc, char **argv)
{
return 0;
}
gcc -static -o foo foo.c
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the uClibc-cvs
mailing list