On Tue, Aug 23, 2011 at 11:34:58PM +0200, Dimitry Andric wrote:
> On 2011-08-21 11:08, Test Rat wrote:
> >I often get corrupted traces with clang world, the cause seems to be in
> >rtld.
> ...
> > (gdb) bt
> > #0 0x0008009455ac in ?? ()
> > #1 0x000800944fa7 in ?? ()
>
> After som
On 2011-08-21 11:08, Test Rat wrote:
I often get corrupted traces with clang world, the cause seems to be in rtld.
...
(gdb) bt
#0 0x0008009455ac in ?? ()
#1 0x000800944fa7 in ?? ()
After some digging, this turned out to be caused by the empty function
r_debug_state() in li
On Sun, Aug 21, 2011 at 11:11:10PM +0400, Test Rat wrote:
> Roman Divacky writes:
>
> >> And compiling rtld with clang + -O0 makes it crash.
> >
> > what is "it" ? clang itself or rtld?
>
> rtld, but not on trunk (r138219)
>
> > Also I think it makes sense to check if this issue persists with T
Roman Divacky writes:
>> And compiling rtld with clang + -O0 makes it crash.
>
> what is "it" ? clang itself or rtld?
rtld, but not on trunk (r138219)
> Also I think it makes sense to check if this issue persists with TOT
> clang, can you check that?
It persists. Compiling only rtld.c with -O0
I often get corrupted traces with clang world, the cause seems to be in rtld.
$ cd /usr/src/libexec/rtld-elf; env -i __MAKE_CONF=/dev/null TERM=$TERM sh
$ make CC=gcc all install
$ gdb yes
[...]
y
y
^C
Program received signal SIGINT, Interrupt.
0x0008009455ac in write () fro
