Subject: Re: matlab stopped working - also kdump output on emulations
To: Jan Schaumann <jschauma@netmeister.org>
From: Mark Davies <mark@mcs.vuw.ac.nz>
List: current-users
Date: 07/21/2004 22:43:16
On Wednesday 21 July 2004 18:00, Mark Davies wrote:
> If ktrace isn't lying to me (which is always possible) looks like its
> trying to call some unimplemented system calls: #91, #168 and #179
Looks like kdump is lying to me. I get different output from my trace if I
"kdump" vs "kdump -e linux" but there are the correct EMUL lines at the
start of each process so shouldn't kdump get this right automatically?
[...]
@@ -9903,13 +9903,13 @@
esac
"
1300 sh RET read 528/0x210
- 1300 sh CALL execve(0x806d204,0x806d238,0x806d244)
+ 1300 sh CALL oldolduname(0x806d204,0x806d238,0x806d244)
1300 sh NAMI "/vol/matlab/R14/bin/glnx86/MATLAB"
1300 sh NAMI "/emul/linux/lib/ld-linux.so.2"
1300 sh NAMI "/emul/linux"
1300 sh NAMI "/emul/linux/lib/ld-linux.so.2"
1300 MATLAB EMUL "linux"
- 1300 MATLAB RET execve -1 errno -2 No such file or directory
+ 1300 MATLAB RET oldolduname -1 errno -2 No such file or directory
1300 MATLAB CALL uname(0xbfffe3dc)
1300 MATLAB RET uname 0
1300 MATLAB CALL brk(0)
@@ -16064,16 +16064,16 @@
1384 MATLAB RET clone 1440/0x5a0
1384 MATLAB CALL kill(0x514, SIGRT0)
1384 MATLAB RET kill 0
- 1300 MATLAB RET #179 (unimplemented) -1 errno -4 Unknown error:
4294967292
+ 1300 MATLAB RET rt_sigsuspend -1 errno -4 Interrupted system call
1300 MATLAB PSIG SIGRT0 caught handler=0x485edfd0 mask=(2,3,18,28))
- 1300 MATLAB CALL #119 (obsolete resuba)(0xbfffae04)
- 1300 MATLAB RET #119 (obsolete resuba) JUSTRETURN
- 1300 MATLAB CALL ntp_gettime(1,0xbfffb770,0,8)
- 1300 MATLAB RET ntp_gettime 0
- 1300 MATLAB CALL fchdir(0)
- 1300 MATLAB RET fchdir 1090388731/0x40fe02fb
- 1300 MATLAB CALL fchdir(0)
- 1300 MATLAB RET fchdir 1090388731/0x40fe02fb
+ 1300 MATLAB CALL sigreturn(0xbfffae04)
+ 1300 MATLAB RET sigreturn -1 errno -2 No such file or directory
+ 1300 MATLAB CALL rt_sigprocmask(1,0xbfffb770,0,8)
+ 1300 MATLAB RET rt_sigprocmask 0
+ 1300 MATLAB CALL time(0)
+ 1300 MATLAB RET time 1090388731/0x40fe02fb
+ 1300 MATLAB CALL time(0)
+ 1300 MATLAB RET time 1090388731/0x40fe02fb
1440 MATLAB EMUL "linux"
1440 MATLAB RET fork 0
1440 MATLAB CALL getpid
@@ -16091,24 +16091,24 @@
[...]
Note also for about 6000 lines at the start of "MATLAB" running the two traces
are in sync then the "kdump" case seems to forget its a linux emulation!
cheers
mark