|
From: Julian S. <js...@ac...> - 2006-01-26 19:24:34
|
Dave > I am running on an IBM Power5 machine running SuSe Enterprise Server 9 > and am getting the following crash when starting up Valgrind (copied > from SVN on 1-18) on any 64 bit program: > ==24861== Process terminating with default action of signal 11 > (SIGSEGV)==24861== Bad permissions for mapped region at address 0x53E0 > ==24861== at 0x53E0: ??? I also tried it out on POWER5 / SLES9 a few days ago and fixed exactly this. It's because the initial PC and toc pointer are not properly relocated (as you also noticed). > Eventually this entry address 0x53e0 will be propagated out to start up > the dynamic linker and get the segfault. My guess is that this value > needs to be relocated relative to 0x400000 but I'm not that familiar > at how this should work. Good detective work. That's exactly the same diagnosis I came to, and I fixed it in valgrind r5576, last Friday. Can you svn up and try again? > If you need more information to re-create this please let me know. > > Is this the correct forum for this sort of report or should I be > submitting a Bugzilla? For code which is currently under active development (you are keeping an eye on the svn commit messages, right?), this is the right kind of place. For stable/official releases, or for bugs in code which hasn't been hacked around recently, bugzilla is better. The line is a bit hazy. > What is the criteria I should use for deciding where to submit future > problem reports? I would only add that if you're reporting bugs against recent dev code, it's worth svn up-ing and rebuilding everything from scratch before chasing a bug. The rate of change can sometimes be very high, as it has been these past couple of weeks for ppc64. Good to see you folks exercising the ppc32/64 port. J |