- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Getting Debug Information from a binary
Operating System - HP-UX
1753546
Members
5540
Online
108795
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-19-2010 04:45 AM
тАО03-19-2010 04:45 AM
Getting Debug Information from a binary
In our code we extract the debug information from the binaries( .so files) that are built using debug mode and store this information in a separate file. This is required because we strip all debug information from the binaries and then ship them to the customer along with the extraction debug information files .
Incase any failure occurrs ,our application will read the debug information from the stored/extracted file and give proper trace information to the user ( with source , line number where error occured etc debug information).
We are working on HP Itanium and we have code in Solaris and Linux which does the extraction of the debug information. But Solaris and Linux supports ELF STAB format while HP Itanium supports DWARF2 format. Basically we need to extract informations like function name , src file names . source code of functions/sybols , size of function, start offset in exe, 1st function in source file, last function in src file, etc(the information in STAB in Solaris) using the DWARF2 format.
In short this is more or less similar to a debugger code .
Is there any open source code or any API which we can re-use to attain this in HP Itanium ( DWARF2 reader )?
Incase any failure occurrs ,our application will read the debug information from the stored/extracted file and give proper trace information to the user ( with source , line number where error occured etc debug information).
We are working on HP Itanium and we have code in Solaris and Linux which does the extraction of the debug information. But Solaris and Linux supports ELF STAB format while HP Itanium supports DWARF2 format. Basically we need to extract informations like function name , src file names . source code of functions/sybols , size of function, start offset in exe, 1st function in source file, last function in src file, etc(the information in STAB in Solaris) using the DWARF2 format.
In short this is more or less similar to a debugger code .
Is there any open source code or any API which we can re-use to attain this in HP Itanium ( DWARF2 reader )?
- Tags:
- debug
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-20-2010 01:40 AM
тАО03-20-2010 01:40 AM
Re: Getting Debug Information from a binary
By default there is no debug info in load modules, +objdebug, it is left in the object files.
You would have to use +noobjdebug.
>we need to extract info like function name, src filenames. size of function, start offset in exe,
This info is already in the minimal line table and you don't need -g to include it.
You would have to use +noobjdebug.
>we need to extract info like function name, src filenames. size of function, start offset in exe,
This info is already in the minimal line table and you don't need -g to include it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-22-2010 01:16 AM
тАО03-22-2010 01:16 AM
Re: Getting Debug Information from a binary
You could look into open source HP-WDB debugger.
It reads DWARF2 debugging information from binary.
You can download WDB and its source files from www.hp.com/go/wdb
The code that does this stuff is in file dwarf2read.c.
Hope this helps you.
It reads DWARF2 debugging information from binary.
You can download WDB and its source files from www.hp.com/go/wdb
The code that does this stuff is in file dwarf2read.c.
Hope this helps you.
- Tags:
- gdb
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP