Hi
I loaded the last svn version and compiled it.
This time it didn't run at all, and got segmentation fault instantly
Here is some gdb output on this :
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc-linux"...
(gdb) run aidc.out
Starting program: /usr/local/sbin/valgrind aidc.out
Executing new program: /usr/local/lib/valgrind/ppc32-linux/memcheck
Program received signal SIGILL, Illegal instruction.
0x380303e4 in vgPlain_machine_get_hwcaps () at m_machine.c:453
453 m_machine.c: No such file or directory.
in m_machine.c
(gdb) bt
#0 0x380303e4 in vgPlain_machine_get_hwcaps () at m_machine.c:453
#1 0x38033158 in _start_in_C_linux (pArgc=0x381dfed0) at m_main.c:1392
#2 0x380307dc in _start ()
It seem the svn is a bit premature, Is it possible to get only the patch
concerning the ELF reader ?
Bugzilla from [email protected] wrote:
>
>
>> >> I also compiled valgring (3.4.0) to my desktop enviroment (Red Hat)
>> and
>> >> it worked fine.
>>
>> Julian and Tom just fixed a problem related to stack traces which
>
> Tom diagnosed and fixed it. I just sat on the sidelines and felt
> vaguely embarrassed at having screwed it up so much :-)
>
>> sounds similar, but I thought that was for AMD64 platform only.
>
> The fix applies to all ELF systems (hence all Linux targets), although
> the problem is most obvious on amd64 because that relies entirely on debug
> info to unwind the stack. By comparison, on {x86,ppc32,ppc64}-linux, the
> stack is self-describing enough to be unwindable without outside
> assistance.
>
>> Maybe
>> try checking out the Valgrind SVN trunk?
>> http://www.valgrind.org/downloads/repository.html
>
> Yes, do try that.
>
> J
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Valgrind-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
>
>
--
View this message in context:
http://www.nabble.com/valgrind-not-printing-symbol-names-despite-debug-information-included-tp21558085p21650403.html
Sent from the Valgrind - Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
