From: "Ryan S. Arnold" <ryan.arnold@gmail.com>
To: acrux <acrux_it@libero.it>
Cc: libc-ports@sourceware.org
Subject: Re: [PATCH] powerpc: 405/440/464/476 support and optimizations
Date: Tue, 24 Jan 2012 17:59:00 -0000 [thread overview]
Message-ID: <CAAKybw_pVu2_iM+KrNzcuFwtsCdD=bfMCu1=kHJfZ2VguzWT9Q@mail.gmail.com> (raw)
In-Reply-To: <20120124184339.a9ca7055.acrux_it@libero.it>
On Tue, Jan 24, 2012 at 11:43 AM, acrux <acrux_it@libero.it> wrote:
> On Tue, 24 Jan 2012 11:19:54 -0600
> "Ryan S. Arnold" <ryan.arnold@gmail.com> wrote:
>
>> On Tue, Jan 24, 2012 at 10:48 AM, acrux <acrux_it@libero.it> wrote:
>> > Program received signal SIGINT, Interrupt.
>> > 0x0ff70c80 in __lll_lock_wait_private () from /home/999/new/work/src/build32/libc.so.6
>> > (gdb) bt
>> > #0 0x0ff70c80 in __lll_lock_wait_private () from /home/999/new/work/src/build32/libc.so.6
>> > #1 0x0febb2e4 in __new_exitfn () from /home/999/new/work/src/build32/libc.so.6
>> > #2 0x0febb338 in __internal_atexit () from /home/999/new/work/src/build32/libc.so.6
>> > #3 0x0fea174c in generic_start_main.clone.0 () from /home/999/new/work/src/build32/libc.so.6
>> > #4 0x0fea1970 in __libc_start_main () from /home/999/new/work/src/build32/libc.so.6
>> > #5 0x00000000 in ?? ()
>>
>> Wow, that is not what I expected at all...
>>
>> I can't imagine that there are other threads at this point but ....
>> (gdb) info threads
>>
>> And if there are, please dump the thread backtrace.
>>
>
>
> root@sam4x0:/home/999/ryan# CPP='gcc -m32 -E -x -c-header' /usr/bin/gdb -x rpcgen.gdb /home/999/new/work/src/build32/elf/ld.so.1
> GNU gdb (GDB) 7.3.1
> Copyright (C) 2011 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "powerpc-unknown-linux-gnu".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from /home/999/new/work/src/build32/elf/ld.so.1...(no debugging symbols found)...done.
> Breakpoint 1 at 0x163c0
>
> Breakpoint 1, 0x206f73c0 in _dl_main_dispatch () from /home/999/new/work/src/build32/elf/ld.so.1
> (gdb) info threads
> Id Target Id Frame
> * 1 process 2609 "ld.so.1" 0x206f73c0 in _dl_main_dispatch () from /home/999/new/work/src/build32/elf/ld.so.1
> (gdb) bt
> #0 0x206f73c0 in _dl_main_dispatch () from /home/999/new/work/src/build32/elf/ld.so.1
> #1 0x00000000 in ?? ()
> (gdb) continue
> Continuing.
> ^C
> Program received signal SIGINT, Interrupt.
> 0x0ff70c80 in __lll_lock_wait_private () from /home/999/new/work/src/build32/libc.so.6
> (gdb) bt
> #0 0x0ff70c80 in __lll_lock_wait_private () from /home/999/new/work/src/build32/libc.so.6
> #1 0x0febb2e4 in __new_exitfn () from /home/999/new/work/src/build32/libc.so.6
> #2 0x0febb338 in __internal_atexit () from /home/999/new/work/src/build32/libc.so.6
> #3 0x0fea174c in generic_start_main.clone.0 () from /home/999/new/work/src/build32/libc.so.6
> #4 0x0fea1970 in __libc_start_main () from /home/999/new/work/src/build32/libc.so.6
> #5 0x00000000 in ?? ()
> (gdb) info threads
> Id Target Id Frame
> * 1 process 2609 "ld.so.1" 0x0ff70c80 in __lll_lock_wait_private () from /home/999/new/work/src/build32/libc.so.6
> (gdb) thread apply all bt full
I wonder if one of the string routine calls in the loader overwrote
its bounds and ended up writing over that lock, hence why the wait is
hanging.
Can you do an (gdb) info frame and try to figure out what the value of
the futex is when it's blocking?
Ryan
Ryan
next prev parent reply other threads:[~2012-01-24 17:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 17:34 Luis Machado
2010-09-03 14:45 ` Ryan Arnold
2010-09-03 15:00 ` Luis Machado
2010-10-04 18:54 ` Luis Machado
2010-12-13 20:26 ` Ryan Arnold
2011-01-18 13:16 ` Ryan Arnold
2011-01-25 21:32 ` Joseph S. Myers
2012-01-18 20:31 ` acrux@cruxppc.org
2012-01-19 19:35 ` Carlos O'Donell
2012-01-20 14:24 ` acrux
2012-01-20 15:52 ` Ryan S. Arnold
2012-01-20 18:03 ` Carlos O'Donell
2012-01-23 0:41 ` acrux
2012-01-23 15:48 ` Ryan S. Arnold
2012-01-24 16:47 ` acrux
2012-01-24 17:20 ` Ryan S. Arnold
2012-01-24 17:41 ` acrux
2012-01-24 17:59 ` Ryan S. Arnold [this message]
2012-02-18 2:06 ` acrux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAKybw_pVu2_iM+KrNzcuFwtsCdD=bfMCu1=kHJfZ2VguzWT9Q@mail.gmail.com' \
--to=ryan.arnold@gmail.com \
--cc=acrux_it@libero.it \
--cc=libc-ports@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).