HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- wdb debugging shared libraries
Operating System - HP-UX
1833861
Members
2411
Online
110063
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
Forums
Discussions
Discussions
Discussions
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
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
09-10-2002 09:38 AM
09-10-2002 09:38 AM
wdb debugging shared libraries
I am trying to step-in into a routine that is part of a shared library.
I found a note related to "privately mapping shared libraries" using
pxdb -s on executable-name
before debugging session.
It is not working for me.
Any help?
I found a note related to "privately mapping shared libraries" using
pxdb -s on executable-name
before debugging session.
It is not working for me.
Any help?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-11-2002 05:05 AM
09-11-2002 05:05 AM
Re: wdb debugging shared libraries
You don't mention what kinds of errors you are getting.
I generally use the pxdb command when I want to attach to a process that is already running. If I have built program A then I do a pxdb -s on A. I can then run A, and while it is running do: gdb A and gdb will attach that process and I can debug the shared libraries within that process.
Things that have kept me from doing this are:
- main programs not compiled -g
- shared libraries not compiled -g
- stripped libraries and binaries
- libraries that are shl_loaded'
I generally use the pxdb command when I want to attach to a process that is already running. If I have built program A then I do a pxdb -s on A. I can then run A, and while it is running do: gdb A
Things that have kept me from doing this are:
- main programs not compiled -g
- shared libraries not compiled -g
- stripped libraries and binaries
- libraries that are shl_loaded'
Necessary questions: Why? What? How? When?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-11-2002 05:11 AM
09-11-2002 05:11 AM
Re: wdb debugging shared libraries
Hi Rick,
There is no error. The debugger (wdb) does not allow me to step into the shared library routine. I've tried it with gdb with the same results.
My method was little different. I used
pxdb -s on executable-name
before using the debugger for the executable.
To my knowledge, the code is compiled with -g option and not stripped. I'd double-check today.
What do you mean by shl_loaded?
Thanks for your reply.
Neeraj
There is no error. The debugger (wdb) does not allow me to step into the shared library routine. I've tried it with gdb with the same results.
My method was little different. I used
pxdb -s on executable-name
before using the debugger for the executable.
To my knowledge, the code is compiled with -g option and not stripped. I'd double-check today.
What do you mean by shl_loaded?
Thanks for your reply.
Neeraj
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP