If you hand me some recipes, I might be able to use the original
machine to help. a verbose dump of the stack... any particular variables
you want to look at?
Scott Emery
emery@xxxxxxx
In message <1235699880.4166.63.camel@xxxxxxxxxxxxxxxxxx>, Nathan Scott writes:
>On Thu, 2009-02-26 at 16:14 -0600, Scott Emery wrote:
>> In message <1235681754.4166.14.camel@xxxxxxxxxxxxxxxxxx>, Nathan Scott write
>s:
>> >Hi Scott,
>> >
>> >Could you mail "core" and "pmcd" to me please?
>> >
>>
>> Mail attachments are tricky for me. Does uuencode/uudecode work
>> for you. If I can anonymous ftp to a server, that would be most convenient.
>> The data is up at SGI.
>
>Thanks for that, and the followup libc I asked for. I'm having
>no luck analysing these though - the gdb and distros I'm using
>(Debian and RHEL5) report wildly wrong stack traces when using
>the installed libc (which doesn't match this binary) and when I
>set LD_LIBRARY_PATH to your libc, gdb segfaults straight away.
>
>Ugh. Only other option I can think of (if none of the other guys
>lurking have SLES10 handy either) is to build a statically linked
>pmcd, capture a core file from that, and resend.
>
>cheers.
>
>--
>Nathan
>
|