Segfault in libdl-0.9.33.so
prushik at gmail.com
Sat Mar 31 14:07:33 UTC 2012
On Fri, Mar 30, 2012 at 10:44 PM, PHilip RUshik <prushik at gmail.com> wrote:
> On Fri, Mar 30, 2012 at 9:12 PM, Filippo ARCIDIACONO <
> filippo.arcidiacono at st.com> wrote:
>> > -----Original Message-----
>> > From: uclibc-bounces at uclibc.org [mailto:uclibc-bounces at uclibc.org] On
>> > Behalf Of PHilip RUshik
>> > Sent: Friday, March 30, 2012 1:03 PM
>> > To: uclibc at uclibc.org
>> > Subject: Segfault in libdl-0.9.33.so
>> > Both ncurses and SDL crash whenever an application using them crashes.
>> > dmesg tells me that sdl related crashes are segfaults in libdl-
>> > 0.9.33.so,
>> > which is (correct me if I'm wrong) the library for the dynamic loader?
>> It is the library provide the support to dynamically load shared
>> > There isn't much more info since I didn't build with debugging
>> > libraries.
>> > Its strange that this is happening, it worked previously, and I don't
>> > think
>> > I changed anything in my uclibc config except for adding fenv
>> > functions,
>> > which shouldn't affect SDL since SDL is only written in C.
>> > Everything on my system is dynamically linked, and most things run fine
>> > including complex applications such as Xfbdev, and even Abiword. Any
>> > ideas
>> > about what the problem could be?
>> With the info you provide is difficult understand where is the problem,
>> What I suggest you is to build the uClibc with SUPPORT_LD_DEBUG and
>> SUPPORT_LD_DEBUG_EARLY enabled, they could give some useful info.
>> Which arch are you using?
>> > If it would be helpful, I could show you my uclibc config file (or
>> > some relevant portion of it).
>> > --PHil
>> > _______________________________________________
>> > uClibc mailing list
>> > uClibc at uclibc.org
>> > http://lists.busybox.net/mailman/listinfo/uclibc
> I know its not much information, sorry. The arch is x86_64, I know its an
> unusual target architecture, sorry about that. It was built with a binutils
> 2.22 and GCC 4.5.3 / 4.6.3 / 4.7.0 (all three resulted in the same problem).
> I'll add those debug options and rebuild everything. I'm starting the
> build now. I'll let you know.
I enabled those config options, but the output (for the SDL crash) was
exactly the same. However, strangely enough, nano started working. So I'm
rebuilding again with even more debugging enabled.
For anybody who is interested, my target is x86_64 and I am building with
gcc 4.6.3. I replied earlier, but once again I accidentally only sent it to
one person instead of the mailing list.
More information about the uClibc