|
From: Phil S. <pp...@us...> - 2009-08-31 17:27:11
|
I just tried the 3.5.0 version of valgrind on Cell BE and was seeing a
number of these errors
--21076-- WARNING: Serious error when reading debug info
--21076-- When reading debug info
from /spu/spethread-21076-124700480/psmap:
--21076-- can't read file to inspect ELF header
Have I misconfigured things (I did not do any thing special to configure),
a problem, or maybe an issue with my application build?
- Phil
|
|
From: Bart V. A. <bar...@gm...> - 2009-09-01 06:30:52
|
On Mon, Aug 31, 2009 at 7:26 PM, Phil Sanders<pp...@us...> wrote: > I just tried the 3.5.0 version of valgrind on Cell BE and was seeing a > number of these errors > > --21076-- WARNING: Serious error when reading debug info > --21076-- When reading debug info > from /spu/spethread-21076-124700480/psmap: > --21076-- can't read file to inspect ELF header > > Have I misconfigured things (I did not do any thing special to configure), > a problem, or maybe an issue with my application build? A lot of code has been changed in the 3.5.0 release, so it's not immediately clear whether this is a configuration issue or a Valgrind issue. Can you please create a bug report for this issue and include the Valgrind output with -v -d added to the Valgrind command line options ? Can you also verify whether this is a new issue in 3.5.0 or whether this also occurred with 3.4.1 ? Bart. |
|
From: Nicholas N. <n.n...@gm...> - 2009-09-01 06:46:30
|
On Tue, Sep 1, 2009 at 4:30 PM, Bart Van Assche<bar...@gm...> wrote: > On Mon, Aug 31, 2009 at 7:26 PM, Phil Sanders<pp...@us...> wrote: >> I just tried the 3.5.0 version of valgrind on Cell BE and was seeing a >> number of these errors >> >> --21076-- WARNING: Serious error when reading debug info >> --21076-- When reading debug info >> from /spu/spethread-21076-124700480/psmap: >> --21076-- can't read file to inspect ELF header >> >> Have I misconfigured things (I did not do any thing special to configure), >> a problem, or maybe an issue with my application build? > > A lot of code has been changed in the 3.5.0 release, so it's not > immediately clear whether this is a configuration issue or a Valgrind > issue. Can you please create a bug report for this issue and include > the Valgrind output with -v -d added to the Valgrind command line > options ? Can you also verify whether this is a new issue in 3.5.0 or > whether this also occurred with 3.4.1 ? I think the fact it's running on a Cell processor is a factor... I didn't know you could even run Valgrind on Cell. /spu/spethread-21076-124700480/psmap presumably relates to one of the SPUs... Nick |