Opteron Stack Woes

[Daniel Jacobowitz]

On Tue, Aug 17, 2004 at 02:44:59PM +0100, David Lecomber wrote:
> Thanks Daniel,
> 
> > readelf -wF is probably your best bet.  But is the only problem the
> > fact that the backtrace didn't stop at _start?
> 
> I've seen worse stack traces than this on the Opteron, particularly one
> that had Lustre kernel patches applied -- but I don't know if that was
> related..  I'll keep an eye out for further problems.
> 
> I figured that the "Incomplete CFI data" might be an issue.  I don't
> know enough about this area yet to do anything..

It's not a problem - take a look in the archive.
> 
> > You might want to investigate why the backtrace didn't stop earlier, at
> > main or at a fortran entry point.  GDB may be confused about
> > main_name().
> 
> Attached is the readelf -wF info, can you see anything wrong with the
> 0x040d7ad entry?

No, it looks fine.



-- 
Daniel Jacobowitz