|
|
|
|
|
|
| Author |
Message |
pankajtakawale *nix forums beginner
Joined: 29 Aug 2005
Posts: 21
|
Posted: Tue Jul 11, 2006 3:22 pm Post subject:
tusc output - confused
|
|
|
this is tusc output:-
[23337] write(1, "1b[ 4 7 ; 1 H 1b[ M \n\n\nP r e ".., 40) ....... = 40
[23337] sigaction(SIGTSTP, 0x4000b07c, NULL) ..................... = 0
[23337] read(0, "\r", 255) ....................................... = 1
[23337] lseek64(8, 0, SEEK_CUR) .................................. = 24
[23337] lseek64(8, 6144, SEEK_SET) ............................... =
6144
[23337] read(8, "\0\0\006\0\0\005\0\0\0\a\0\0\010".., 1024) ...... =
1024
[23337] lseek64(8, 24, SEEK_SET) ................................. = 24
[23337] lseek64(8, 0, SEEK_CUR) .................................. = 24
[23337] lseek64(8, 4096, SEEK_SET) ............................... =
4096
[23337] read(8, "\0\0\004\0\0\003\0\0\0\n\0\0\010".., 1024) ...... =
1024
[23337] lseek64(8, 24, SEEK_SET) ................................. = 24
[23337] Received signal 10, SIGBUS, in user mode, [caught], partial
siginfo
[23337] Siginfo: si_code: I_NONEXIST, faulting address: 0x4003f15b,
si_errno: 0
[23337] PC: 0xc12b7317, instruction: 0x0c601094
Above trace doesnt show the actual culprit/victim system call.
Im just guessing that it is while reading the file.
What can be the cause of SIGBUS? reading corrupt file? |
|
| Back to top |
|
 |
Rick Jones *nix forums Guru
Joined: 24 Feb 2005
Posts: 492
|
Posted: Tue Jul 11, 2006 5:53 pm Post subject:
Re: tusc output - confused
|
|
|
knowledgeseeker <pankaj.takawale@gmail.com> wrote:
| Quote: | this is tusc output:-
[23337] write(1, "1b[ 4 7 ; 1 H 1b[ M \n\n\nP r e ".., 40) ....... = 40
[23337] sigaction(SIGTSTP, 0x4000b07c, NULL) ..................... = 0
[23337] read(0, "\r", 255) ....................................... = 1
[23337] lseek64(8, 0, SEEK_CUR) .................................. = 24
[23337] lseek64(8, 6144, SEEK_SET) ............................... =
6144
[23337] read(8, "\0\0\006\0\0\005\0\0\0\a\0\0\010".., 1024) ...... =
1024
[23337] lseek64(8, 24, SEEK_SET) ................................. = 24
[23337] lseek64(8, 0, SEEK_CUR) .................................. = 24
[23337] lseek64(8, 4096, SEEK_SET) ............................... =
4096
[23337] read(8, "\0\0\004\0\0\003\0\0\0\n\0\0\010".., 1024) ...... =
1024
[23337] lseek64(8, 24, SEEK_SET) ................................. = 24
[23337] Received signal 10, SIGBUS, in user mode, [caught], partial
siginfo
[23337] Siginfo: si_code: I_NONEXIST, faulting address: 0x4003f15b,
si_errno: 0
[23337] PC: 0xc12b7317, instruction: 0x0c601094
Above trace doesnt show the actual culprit/victim system call.
Im just guessing that it is while reading the file.
What can be the cause of SIGBUS? reading corrupt file?
|
IIRC it doesn't have to have been any of those system calls - the
SIGBUS could be for the application code chasing a bad pointer.
You might want to look at the core file with wdb (gdb) and see what
the stack trace tells you.
rick jones
--
The computing industry isn't as much a game of "Follow The Leader" as
it is one of "Ring Around the Rosy" or perhaps "Duck Duck Goose."
- Rick Jones
these opinions are mine, all mine; HP might not want them anyway...
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH... |
|
| Back to top |
|
 |
Paul Pluzhnikov *nix forums Guru
Joined: 25 Mar 2005
Posts: 512
|
Posted: Wed Jul 12, 2006 2:20 am Post subject:
Re: tusc output - confused
|
|
|
Rick Jones <rick.jones2@hp.com> writes:
| Quote: | knowledgeseeker <pankaj.takawale@gmail.com> wrote:
....
Above trace doesnt show the actual culprit/victim system call.
|
Because system call is not a culprit, nor a victim.
| Quote: | What can be the cause of SIGBUS? reading corrupt file?
|
A bug in the program.
| Quote: | IIRC it doesn't have to have been any of those system calls
|
It's even stronger than that: there are *no* system calls (other than
"kill(getpid(), SIGBUS);" that is) which by themselves will cause
SIGBUS to be delievered to a process.
Cheers,
--
In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email. |
|
| Back to top |
|
 |
Dennis Handly *nix forums beginner
Joined: 28 Jun 2005
Posts: 38
|
Posted: Sat Jul 15, 2006 4:23 am Post subject:
Re: tusc output - confused
|
|
|
Eric Gouriou wrote:
: > Received signal 10, SIGBUS, in user mode, [caught], partial siginfo
: > Siginfo: si_code: I_NONEXIST, faulting address: 0x4003f15b,
: > PC: 0xc12b7317, instruction: 0x0c601094
: It is most likely due to reading multiple bytes at an incorrectly aligned
: address, in this case 0x4003f15b.
Exactly, the instruction is: LDWS 0(r3),r20
So R3 is misaligned.
: Tusc is the wrong tool for this job.
: Eric
It will only give you the PC, data address and the instruction. |
|
| Back to top |
|
 |
Ulrich Windl *nix forums addict
Joined: 07 Mar 2005
Posts: 92
|
Posted: Tue Jul 18, 2006 7:42 am Post subject:
Re: tusc output - confused
|
|
|
"knowledgeseeker" <pankaj.takawale@gmail.com> writes:
| Quote: | this is tusc output:-
[...]
[23337] lseek64(8, 24, SEEK_SET) ................................. = 24
[23337] Received signal 10, SIGBUS, in user mode, [caught], partial
siginfo
[23337] Siginfo: si_code: I_NONEXIST, faulting address: 0x4003f15b,
si_errno: 0
[23337] PC: 0xc12b7317, instruction: 0x0c601094
Above trace doesnt show the actual culprit/victim system call.
|
I think tusc is printing the system call after it has returned (to show you
the result).
| Quote: | Im just guessing that it is while reading the file.
What can be the cause of SIGBUS? reading corrupt file? |
|
|
| Back to top |
|
 |
Google
|
|
| Back to top |
|
 |
|
|
The time now is Mon Dec 01, 2008 10:18 pm | All times are GMT
|
|
Cheapest mobile phones | Adverse Credit Remortgage | Facebook Proxy | Bicicletas | Bad Credit Debt Consolidation
|
|
Copyright © 2004-2005 DeniX Solutions SRL
|
|
|
|
Other DeniX Solutions sites:
Unix/Linux blog |
electronics forum |
medicine forum |
science forum |
|
|
Privacy Policy
|
Powered by phpBB © 2001, 2005 phpBB Group
|
|