*
*Home|Chinese|Japanese*About ARM|Forums|Events|News|Employment|Contact Us|Investors*
dotted rule
*ARM - the architecture for the digital worldARM - the architecture for the digital world
search
*
*
***
*MARKETS:PRODUCTS & SOLUTIONS:CONNECTED COMMUNITY:TECHNICAL SUPPORT:DOCUMENTATION*
*
technical support
*
*
****
*.Technical Support
*
*
*>>Home Page*
*
*.Obtaining Support*
*
*.FAQs*
*
**Development Tool FAQs*
**IP FAQs*
**Embedded Software FAQs*
**Artisan Physical IP FAQs (Login Required)*
*
*.Downloads*
*
*.Documentation*
*
*.Training*
*
*.Where To Buy*
*
*.Keil MCU Tools*
*
*.What's New*
*
*.ARM Newsgroups*
*
*.Active Assist On-site Services*
*
*
*
technical support FAQsask ARM*
*

Technical Support Search
*     (Advanced Search)
  FAQs   Documentation   Downloads   Forums

*

 
downarrowCan I debug Linux Applications and Kernel modules using RVD?
Applies to: RVD Debug, RealView Development Suite (RVDS) 3.0, RealView Development Suite (RVDS) 3.1

No. We recommend the GDB debugger is used for this purpose (KGDB can be used for kernel modules). The latest GNU tools for the ARM architecture are available for download from the CodeSourcery website: www.codesourcery.com

Linux kernel modules and applications contain relocatable sections without absolute address information. They rely on the kernel's dynamic loader to relocate image code and/or data sections to their final execution address on the target. The relocation process only takes place once the application or module is loaded by the kernel (For kernel modules this is normally initiated using the "insmod" command). Loading the image symbols in RVD will therefore not use the relocated addresses as allocated by the kernel.

Furthermore, context switching between Linux applications (all executing code from the same virtual address) will prevent RVD from knowing which process it is currently debugging.






back to top

*
**
*4 dots*Other ARM Websites
*
shadow *LEGAL STATEMENTshadow