- Community Home
- >
- HPE Community, Korea
- >
- HP-UX
- >
- q4 실행시 에러 해결 요청
HP-UX
1753797
회원
7338
온라인
108799
솔루션
포럼
범주
Company
Local Language
뒤로
포럼
토론 게시판
포럼
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
토론 게시판
토론 게시판
포럼
토론 게시판
뒤로
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
블로그
정보
커뮤니티 언어
언어
포럼
블로그
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
날짜: 11-24-2004 11:00 PM
날짜: 11-24-2004 11:00 PM
q4 실행시 에러 해결 요청
안녕하세요. q4를 실행하면 아래와 같이 나타납니다. 메뉴얼상에도
특별한 대처방법이 없네요..
고수님들의 한마디 부탁드립니다.
@(#) q4 $Revision: B.11.20f $ $Fri Aug 17 18:05:11 PDT 2001 0
Reading kernel symbols ...
This kernel does not look like it has been prepared for debugging.
If this is so, you will need to run pxdb or q4pxdb64 on it
before you can use q4.
You can verify that this is the problem by asking pxdb:
$ pxdb -s status ./vmunix
If pxdb says the kernel has not been preprocessed, you will need to run
it on the kernel before using q4:
$ pxdb ./vmunix
Be aware that pxdb will overwrite your kernel with the fixed-up version,
so you might want to save a copy of the file before you do this.
(If the "-s status" command complained about an internal error,
you will need to get a different version of pxdb before proceeding.)
If you were not able to find pxdb, be advised that it moved from its
traditional location in /usr/bin to /opt/langtools/bin when the change
was made to the System V.4 file system layout.
If you do not have pxdb, it is probably because the debugging tools are
now an optional product (associated with the compilers and debuggers)
and are no longer installed on every system by default.
In this case you should use q4pxdb64 in exactly the same manner as you would
use pxdb.
quit
특별한 대처방법이 없네요..
고수님들의 한마디 부탁드립니다.
@(#) q4 $Revision: B.11.20f $ $Fri Aug 17 18:05:11 PDT 2001 0
Reading kernel symbols ...
This kernel does not look like it has been prepared for debugging.
If this is so, you will need to run pxdb or q4pxdb64 on it
before you can use q4.
You can verify that this is the problem by asking pxdb:
$ pxdb -s status ./vmunix
If pxdb says the kernel has not been preprocessed, you will need to run
it on the kernel before using q4:
$ pxdb ./vmunix
Be aware that pxdb will overwrite your kernel with the fixed-up version,
so you might want to save a copy of the file before you do this.
(If the "-s status" command complained about an internal error,
you will need to get a different version of pxdb before proceeding.)
If you were not able to find pxdb, be advised that it moved from its
traditional location in /usr/bin to /opt/langtools/bin when the change
was made to the System V.4 file system layout.
If you do not have pxdb, it is probably because the debugging tools are
now an optional product (associated with the compilers and debuggers)
and are no longer installed on every system by default.
In this case you should use q4pxdb64 in exactly the same manner as you would
use pxdb.
quit
2 응답 2
위에 명시된 의견은 Hewlett Packard Enterprise가 아닌 저자의 개인 의견입니다. 이 사이트를 사용하면 이용 약관에 동의하게되며 참여 규칙 .
뉴스 및 이벤트
© Copyright 2024 Hewlett Packard Enterprise Development LP