View Single Post
  #6   Spotlight this post!  
Unread 01-20-2009, 07:41 PM
gvarndell's Avatar
gvarndell gvarndell is offline
Software Engineer
AKA: Addi's and Georgie's Dad
FRC #1629 (GaCo)
Team Role: Parent
 
Join Date: Jan 2009
Rookie Year: 2008
Location: Grantsville, Maryland
Posts: 350
gvarndell has a reputation beyond reputegvarndell has a reputation beyond reputegvarndell has a reputation beyond reputegvarndell has a reputation beyond reputegvarndell has a reputation beyond reputegvarndell has a reputation beyond reputegvarndell has a reputation beyond reputegvarndell has a reputation beyond reputegvarndell has a reputation beyond reputegvarndell has a reputation beyond reputegvarndell has a reputation beyond repute
Re: Disassemble VxWorks (WindRiver) ELF Binaries?

Quote:
Originally Posted by GeneralFailure View Post
Perfect, this is exactly what I needed to get the disassembly.

Any tips for the address space? The exception address doesn't match any of the addresses in the binary -- I assume they've been relocated.

I've got a Task address, but it doesn't seem to correspond to an address in the ELF binary either.
What is the exception? What is the address?
The exception address is where the PC was when the exception happened.
It's probably in one of the DKMs that get downloaded to the target.
This can be tricky because you can't easily 'predict' where the kernel will load DKMs.
However, you can 'see' where they actually got loaded by typing 'moduleShow' in the taget console.
Reply With Quote