Richard Hadsell wrote:
> I'll try to build a -g version of libdl, so that I can step through
> the dlerror call. I don't know how to do that, yet, but I'll try to
> get some help.
This may be my last contribution on this thread, because I'm stuck. I
built a debug version of libdl and stepped into the code.
The call to __libc_getspecific on line 53 returns a valid pointer. The
dl_action_result struct has 0 for data members errcode, returned, and
objname, but its errstring pointer is bad (0x00000089). The seg fault
happens after it goes into the call to __asprintf on lines 71-73 with
the bad pointer in buf.
I can't step into __libc_getspecific, even with a debug version of the
pthreads library. I have no idea where it is going, and I probably
couldn't figure out what's happening with the thread-specific data
anyway. So I'm stuck.
I still think there might be a problem in LAM code somewhere. Does
anyone know whether mpirun or lamd use any thread-specific data? It's
way beyond me at the moment.
--
Dick Hadsell 914-259-6320 Fax: 914-259-6499
Reply-to: hadsell_at_[hidden]
Blue Sky Studios http://www.blueskystudios.com
44 South Broadway, White Plains, NY 10601
|
