> I'm not sure how intentionally corrupting the stack with a debugger to
> cause a segfault constitutes a glibc bug...
Setting the auxiliary vector to empty is not really "corrupting" it. You
just need to ask yourself whether you consider it acceptable for the C
library to segfault when presented
Perhaps I should mention the keyword "locale" here. It seems pretty
clear that the segfault is caused by strtol_l_internal receiving a
null pointer as its locale argument. So the C library start-up code,
when presented with an empty auxiliary vector, is silently failing to
initialise the locale
Public bug reported:
The auxiliary vector is put onto a process's stack by the kernel and it
normally isn't empty. However, the C library is probably supposed to
cope with the auxiliary vector being empty (you might be running the
program under a different or a modified operating system). Therefor
Public bug reported:
Binary package hint: gcc-4.4
// This code gives a spurious
// "warning: array subscript is above array bounds"
// with gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)
// when compiled with: gcc -c -O2 -Wall
struct s { int a[100]; };
void f(struct s *ps, int i)
{
int *a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/732711
Title:
gcc-4.4 gave spurious "warning: array subscript is above array bounds"
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
