|
From: Eduardo M. <ea...@us...> - 2005-11-14 17:26:36
|
I checked out the latest valgrind code from 3.0 development trunk and I=20 still get the illegal Instruction running valgrind. valgrind-3.1.SVN (revision 1458.) >valgrind --version Illegal instruction > Regards, Eduardo A. Mu=F1oz Julian Seward <ju...@va...>=20 11/14/2005 10:38 AM To Eduardo Munoz/Austin/IBM@IBMUS cc Subject Re: [Valgrind-users] Support questions: ppcnf, helgrind,and addrcheck On Monday 14 November 2005 16:28, you wrote: > When I check out the code from 3.0 valgrind development trunk: > > svn co svn://svn.valgrind.org/valgrind/trunk valgrind > > it says: > > " Checked out revision 1458." Did you miss this? Updated to revision 5129. Try it and see how far you get now. J |
|
From: Eduardo M. <ea...@us...> - 2005-11-14 20:54:08
|
I did what you told to do. Checkout the latest code from svn, rebuilt ,=20 and run valgrind -d -d -v -v --tool=3Dnone ls. I am running valgrind in a ppc nfu system IBM 4xx system. >>>:~ # valgrind -d -d -v -v --tool=3Dnone ls --32569:1:debuglog DebugLog system started by Stage 1, level 2 logging=20 requested --32569:1:launcher tool 'none' requested --32569:1:launcher no platform detected, defaulting platform to=20 'ppc32-linux' --32569:1:launcher launching /usr/lib/valgrind/ppc32-linux/none --32569:1:debuglog DebugLog system started by Stage 2 (main), level 2=20 logging rd --32569:1:main Welcome to Valgrind version 3.1.SVN debug logging --32569:1:main Checking current stack is plausible --32569:1:main Checking initial stack was noted --32569:1:main Starting the address space manager --32569:2:aspacem sp=5Fat=5Fstartup =3D 0x007FFFF880 (supplied) --32569:2:aspacem minAddr =3D 0x0004000000 (computed) --32569:2:aspacem maxAddr =3D 0x007FFFEFFF (computed) --32569:2:aspacem cStart =3D 0x0004000000 (computed) --32569:2:aspacem vStart =3D 0x0042000000 (computed) --32569:2:aspacem suggested=5Fclstack=5Ftop =3D 0x007EFFFFFF (computed) --32569:2:aspacem <<< SHOW=5FSEGMENTS: Initial layout (5 segments, 0=20 segnames) --32569:2:aspacem 0: RSVN 0000000000-0003FFFFFF 64m ----- SmFixed --32569:2:aspacem 1: 0004000000-0041FFFFFF 992m --32569:2:aspacem 2: RSVN 0042000000-0042000FFF 4096 ----- SmFixed --32569:2:aspacem 3: 0042001000-007FFFEFFF 991m --32569:2:aspacem 4: RSVN 007FFFF000-00FFFFFFFF 2048m ----- SmFixed --32569:2:aspacem >>> --32569:2:aspacem Reading /proc/self/maps --32569:2:aspacem <<< SHOW=5FSEGMENTS: With contents of /proc/self/maps = (11 se) --32569:2:aspacem ( 0) /usr/lib/valgrind/ppc32-linux/none --32569:2:aspacem 0: RSVN 0000000000-0003FFFFFF 64m ----- SmFixed --32569:2:aspacem 1: 0004000000-0041FFFFFF 992m --32569:2:aspacem 2: RSVN 0042000000-0042000FFF 4096 ----- SmFixed --32569:2:aspacem 3: 0042001000-006FFFFFFF 735m --32569:2:aspacem 4: FILE 0070000000-0070131FFF 1253376 r-x-- d=3D0x00= B=20 i=3D18) --32569:2:aspacem 5: 0070132000-0070140FFF 61440 --32569:2:aspacem 6: FILE 0070141000-0070141FFF 4096 rw--- d=3D0x00= B=20 i=3D18) --32569:2:aspacem 7: ANON 0070142000-007075FFFF 6414336 rwx-- --32569:2:aspacem 8: 0070760000-007FFFEFFF 248m --32569:2:aspacem 9: ANON 007FFFF000-007FFFFFFF 4096 rw--- --32569:2:aspacem 10: RSVN 0080000000-00FFFFFFFF 2048m ----- SmFixed --32569:2:aspacem >>> --32569:1:main Address space manager is running --32569:1:main Starting the dynamic memory manager --32569:1:mallocfr newSuperblock at 0x42001000 (pszB 1048560) owner=20 VALGRIND/tol --32569:1:main Dynamic memory manager is running --32569:1:main Getting stage1's name --32569:1:main Get hardware capabilities ... Illegal instruction >>>:~ # This is all I get. Regards, Eduardo A. Mu=F1oz Julian Seward <ju...@va...>=20 11/14/2005 12:20 PM To Eduardo Munoz/Austin/IBM@IBMUS cc Subject Re: [Valgrind-users] Support questions: ppcnf, helgrind,and addrcheck On Monday 14 November 2005 17:27, you wrote: > I checked out the latest valgrind code from 3.0 development trunk and I > still get the illegal Instruction running valgrind. > valgrind-3.1.SVN (revision 1458.) > > >valgrind --version > > Illegal instruction Do you want to explain how you think we can debug your problem if you supply us with zero information? Delete your entire build tree and check out again from svn. Rebuild. Run this valgrind -d -d -v -v --tool=3Dnone ls and send the results. J |
|
From: Julian S. <ju...@va...> - 2005-11-15 01:21:03
|
> --32569:1:main Dynamic memory manager is running
> --32569:1:main Getting stage1's name
> --32569:1:main Get hardware capabilities ...
> Illegal instruction
Hmm. Now that really shouldn't happen. Two questions. Firstly,
what Linux kernel version and distribution are you using?
And secondly, if you compile and run the attached program (normally,
not on V), what result do you get?
J
#include <stdio.h>
#include <signal.h>
#include <setjmp.h>
jmp_buf env;
void hdlr_fp ( int x ) { longjmp(env,1); }
void hdlr_vmx ( int x ) { longjmp(env,1); }
int main ( void )
{
sigset_t saved_set, tmp_set;
struct sigaction saved_act, tmp_act;
int have_fp, have_vmx;
sigemptyset(&tmp_set);
sigaddset(&tmp_set, SIGILL);
sigprocmask(SIG_UNBLOCK, &tmp_set, &saved_set);
sigaction(SIGILL, NULL, &saved_act);
tmp_act = saved_act;
tmp_act.sa_flags &= ~SA_RESETHAND;
tmp_act.sa_flags &= ~SA_SIGINFO;
tmp_act.sa_handler = hdlr_fp;
sigaction(SIGILL, &tmp_act, NULL);
have_fp = 1;
if (setjmp(env)) {
have_fp = 0;
} else {
__asm__ __volatile__("fmr 0,0");
}
tmp_act.sa_handler = hdlr_vmx;
sigaction(SIGILL, &tmp_act, NULL);
have_vmx = 1;
if (setjmp(env)) {
have_vmx = 0;
} else {
__asm__ __volatile__("vor 0,0,0");
}
sigaction(SIGILL, &saved_act, NULL);
sigprocmask(SIG_SETMASK, &saved_set, NULL);
printf("fp %d vmx %d\n", have_fp, have_vmx);
return 0;
}
|