- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: gdb 5.2 (wdb) problem
Operating System - Linux
1753513
Members
5340
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
тАО01-24-2006 06:56 AM
тАО01-24-2006 06:56 AM
gdb 5.2 (wdb) problem
I'm getting an error when attempting to run gdb against a process. Here is a sample of the error, any ideas ? TIA
going to run gdb -nx --batch --command 21331/commands /v100u/psoft/psfs8uat/bin/PSAPPSRV 18148
ttrace_wait: No child processes.
n.
21331/commands:1: Error in sourced command file:
Couldn't read register flags (#0): Invalid argument
Quitting: ttrace: Permission denied.
=== gdb 18148
(no debugging symbols found)
--- gdb 18148
going to run gdb -nx --batch --command 21331/commands /v100u/psoft/psfs8uat/bin/PSAPPSRV 18148
ttrace_wait: No child processes.
n.
21331/commands:1: Error in sourced command file:
Couldn't read register flags (#0): Invalid argument
Quitting: ttrace: Permission denied.
=== gdb 18148
(no debugging symbols found)
--- gdb 18148
- Tags:
- gdb
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-25-2006 04:56 AM
тАО01-25-2006 04:56 AM
Re: gdb 5.2 (wdb) problem
Can you tell what exactly you have in 21331/commands file? Also, please make sure that the process with pid 18148 is live at attach time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-25-2006 05:20 AM
тАО01-25-2006 05:20 AM
Re: gdb 5.2 (wdb) problem
Thanks for your response. This is the contents of the commands file:
set height 0
echo \n
echo ==== Thread Information\n
info thread
echo ---- Thread Information\n\n
echo ==== Backtraces\n
thread apply all backtrace 500
echo ---- Backtraces\n\n
echo ==== Shared Libraries\n
info sharedlibrary
echo ---- Shared Libraries\n\n
echo ==== Local Backtrace\n
backtrace 500
echo ---- Local Backtrace\n\n
detach
set height 0
echo \n
echo ==== Thread Information\n
info thread
echo ---- Thread Information\n\n
echo ==== Backtraces\n
thread apply all backtrace 500
echo ---- Backtraces\n\n
echo ==== Shared Libraries\n
info sharedlibrary
echo ---- Shared Libraries\n\n
echo ==== Local Backtrace\n
backtrace 500
echo ---- Local Backtrace\n\n
detach
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-26-2006 04:48 AM
тАО01-26-2006 04:48 AM
Re: gdb 5.2 (wdb) problem
It looks like the debuggee process died while gdb is debuggee. Can you make sure this happened? I.e., check if 18148 is in ps output.
Also, try issuing the commands at gdb command prompt and see which command is cauing the problem. For this, you want to start up gdb without --batch and --command options.
Also, try issuing the commands at gdb command prompt and see which command is cauing the problem. For this, you want to start up gdb without --batch and --command options.
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