- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Examining REGISTERS, address/long variable content...
Operating System - OpenVMS
1753481
Members
4343
Online
108794
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-11-2006 04:56 AM
тАО01-11-2006 04:56 AM
Examining REGISTERS, address/long variable contents from DEBUGGER
Hi,
Env: Alpha DS10/OpenVMS 8.2/VAX MACRO/DEBUGGER
I am debugging MACRO program called from HPs C and C++.
Our documents says we can not see(examine) the "VALUE" stored in REGISTERS, PC, STACK, and some the operand valiable (LONG, WORD, ADDRESS, BLKB) used in difft way addressing modes.
Is there any otherway/method/third party tools using which can we examine the contents memory locations in difft addresing mode.
Thanks
Archunan
Env: Alpha DS10/OpenVMS 8.2/VAX MACRO/DEBUGGER
I am debugging MACRO program called from HPs C and C++.
Our documents says we can not see(examine) the "VALUE" stored in REGISTERS, PC, STACK, and some the operand valiable (LONG, WORD, ADDRESS, BLKB) used in difft way addressing modes.
Is there any otherway/method/third party tools using which can we examine the contents memory locations in difft addresing mode.
Thanks
Archunan
Regards
Archie
Archie
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2006 12:51 AM
тАО01-12-2006 12:51 AM
Re: Examining REGISTERS, address/long variable contents from DEBUGGER
Are your C/C++ and Macro code are all built with any compiler optimizations "off" and "debug" on? Is the source is available to the debugger during run-time? Have you tried to "step into" the macro module while walking through the high-level language code?
Using SDA you could set the context to the target process and examine the registers and any other memory locations (you want the process paused at some known processing location first I'd imagine). An "exa/all" command will reveal nearly everything if you have a linker map to reference.
Using SDA you could set the context to the target process and examine the registers and any other memory locations (you want the process paused at some known processing location first I'd imagine). An "exa/all" command will reveal nearly everything if you have a linker map to reference.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2006 01:17 AM
тАО01-12-2006 01:17 AM
Re: Examining REGISTERS, address/long variable contents from DEBUGGER
Register values can be seen in the debugger register display.
I don't understand what you mean by difft addresing mode.
I don't understand what you mean by difft addresing mode.
____________________
Purely Personal Opinion
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2006 07:32 AM
тАО01-12-2006 07:32 AM
Re: Examining REGISTERS, address/long variable contents from DEBUGGER
Ian/Jim,
thanks for your responses.
Jim: Yes I am going thru step by step of C/C++ and stepped into MACRO programs.
Ian: As of I knew there are 16 addressing modes. I found register-display displays only the address in almost all the addressing modes except "register addresing mode". The register deferred addressing mode, auto increment/decrement, displacement, indexed and other Program counter modes all display only the address. But mostly address only.
Example: Autoincrement deferred mode,
"@(Rn)+", this takes initial contents of the register as the address of indirect longword in memory; the register is then incremented by 4 (length of the indirect longword operand). Then the contents of the indirect longword are retrieved from memory, and that is the final effective address for the operand. Just playing with memory locations and finally pointing the address of low-order byte of the eff address to any operand variable. This varibale can be examined. But before that while traversing through the memory locations, is there any possiblity of seeing what is the contents on any particular mem locations.
Ian looks very hard, I don't know any other way to trace the values while debugging.
I will appreciate any help further on this.
Archunan
thanks for your responses.
Jim: Yes I am going thru step by step of C/C++ and stepped into MACRO programs.
Ian: As of I knew there are 16 addressing modes. I found register-display displays only the address in almost all the addressing modes except "register addresing mode". The register deferred addressing mode, auto increment/decrement, displacement, indexed and other Program counter modes all display only the address. But mostly address only.
Example: Autoincrement deferred mode,
"@(Rn)+", this takes initial contents of the register as the address of indirect longword in memory; the register is then incremented by 4 (length of the indirect longword operand). Then the contents of the indirect longword are retrieved from memory, and that is the final effective address for the operand. Just playing with memory locations and finally pointing the address of low-order byte of the eff address to any operand variable. This varibale can be examined. But before that while traversing through the memory locations, is there any possiblity of seeing what is the contents on any particular mem locations.
Ian looks very hard, I don't know any other way to trace the values while debugging.
I will appreciate any help further on this.
Archunan
Regards
Archie
Archie
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