On Wed, Mar 21, 2012 at 10:06 PM, Khem Raj <[email protected]> wrote: > On Wed, Mar 21, 2012 at 9:55 PM, Kamble, Nitin A > <[email protected]> wrote: >>> On Wed, Mar 21, 2012 at 6:58 PM, Kamble, Nitin A >>> <[email protected]> wrote: >>> > Actually we noticed that Eric’s working sdk gdb was getting linked >>> with the >>> > host libpython.so, And if it is linked with the sdk libpython.so then >>> he is >>> > able to see same issue what I am seeing. >>> > >>> > So look like issue is in the generated libpython.so. >>> > >>> > And in failing case, somehow ldd is not reporting that sdk gdb is >>> > dynamically linked with libpython.so. That is also strange. >>> > >>> >>> OK can you generate the gdb core and post it. I can debug whats causing >>> it. >>> >> >> Khem, >> Thanks for helping out. I also have uploaded the core file here: >> http://min.us/mbii28QmkZ > > ok also try setting MALLOC_CHECK_=2 in environment and run gdb again > this should dump the core > I dont have gdb handy right now its building
just for test try to move sysroots/x86_64-pokysdk-linux/usr/lib/python2.7/lib-dynload/readline.so out of way and retry see if this works ? _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
