Using IDEBUG on AIX 5.2


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Using IDEBUG on AIX 5.2
# 1  
Old 07-14-2006
Using IDEBUG on AIX 5.2

I am trying to run the interactive debugger locally on our new unix machine.
When I type idebug I get 'execute permission denied'. When I look at idebug in /usr/idebug it has all file permissions turned on. I have tried executing using root with the same results.

Anyone familar with idebug??

Thanks in advance.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. AIX

Samba 3.6 on AIX 7.1 - Windows 10 Access to AIX file shares using Active Directory authentication

I am running AIX 7.1 and currently we have samba 3.6.25 installed on the server. As it stands some AIX folders are shared that can be accessed by certain Windows users. The problem is that since Windows 10 the guest feature no longer works so users have to manually type in their Windows login/pwd... (14 Replies)
Discussion started by: linuxsnake
14 Replies

2. UNIX for Beginners Questions & Answers

New to AIX: How do I setup high availability on an AIX System

I am new to AIX but not new to unix. I have an interview for an AIX systems admin position and I know they want someone who has knowledge of High Availability, Failover and LPARs From my research so far, It appear powerha is used to setup high availability and failover on Power systems but is... (2 Replies)
Discussion started by: mathisecure
2 Replies

3. AIX

Will it affect my AIX LPAR security, when i set up email alerts on AIX server.

Hello, I've set up email alerts on AIX Servers. so that i can get email notifications (via mail relay server) when ever there is abnormal behavior. for example 1) my script monitors CPU/disk/memory etc... when it reaches high water ark, it will send an email alert. 2) disk usage alerts 3)... (5 Replies)
Discussion started by: System Admin 77
5 Replies

4. AIX

Nim on AIX 7.1 used to migrate AIX 5.3 to AIX 6.1...is possible?

Using nimadm: nimadm -j nimadmvg -c sap024 -s spot_6100 -l lpp_6100 -d "hdisk1" -Y Initializing the NIM master. Initializing NIM client sap024. 0505-205 nimadm: The level of bos.alt_disk_install.rte installed in SPOT spot_6100 (6.1.3.4) does not match the NIM master's level (7.1.1.2).... (2 Replies)
Discussion started by: sciacca75
2 Replies

5. AIX

How to upgrade AIX Firmware & TL Maintenance Level in AIX

Steps to upgrade AIX TL ( technology Level ) / Maintenance Level in AIX ( including Firmware HMC VIOS ) This article or post covers upgrades for - Hardware Management Console ( HMC ) - Firmware ( also known as microcode ) - VIO ( Virtual I/O Server = PowerVM ) - AIX Version, Technology... (2 Replies)
Discussion started by: filosophizer
2 Replies

6. AIX

IY17981 fix required for aix 4.3.3 to aix 5L migration but not found

Hi, redbook documentation is telling that IY17981 fix is required for aix 4.3.3 to aix 5L migration. But there is no mention about that fix in any ML installation packages. - My system is ML11 : oslevel –r 4330-11 - But xlC.rte is on wrong version : lslpp -L xlC.rte xlC.rte ... (3 Replies)
Discussion started by: astjen
3 Replies

7. AIX

How to apply aix 5.3 TL8 properly on ML5 aix system ?

Is it necessary to put system into single user mode for applying aix 5.3 TL8 on a aix 5.3.5.0 system ? Is the TL8 installation not totally safe ? thank you. (6 Replies)
Discussion started by: astjen
6 Replies

8. UNIX for Dummies Questions & Answers

Executing idebug in AIX

There is an interactive debugger on our AIX box. According to the IBM provided doc, if you type the command IDEBUG The debugger will start. When I do this I get ksh: idebug: 0403-006 Execute permission denied How can I tell what the permissions on that commmand are?? I have... (3 Replies)
Discussion started by: jbrubaker
3 Replies
Login or Register to Ask a Question
idebug(n)																 idebug(n)

__________________________________________________________________________________________________________________________________________________

NAME
idebug - Interactive debugging environment in TkCon SYNOPSIS
idebug body ?level? idebug break ?id? idebug {echo ?id?} ?args? idebug id ?id? idebug off idebug on ?id? idebug {puts ?id?} args idebug show type ?level? ?VERBOSE? idebug trace ?level? _________________________________________________________________ DESCRIPTION
The idebug command provides an interactive debugging environment for procedures via TkCon. You can place idebug break commands into your procedure to create breakpoints. It will pop up the TkCon console and put you into a "debugging" mode. The body, show & trace methods are intended for internal use only. This procedure works for minimal debugging sessions. Comments are encouraged. idebug body ?level? Prints out the body of the command (if it is a procedure) at the specified level. level defaults to the current level. idebug break ?id? Creates a breakpoint within a procedure. This will only trigger if idebug is on and the id matches the pattern. If so, TkCon will pop to the front with the prompt changed to an idebug prompt. You are given the basic ability to observe the call stack an query/set variables or execute Tcl commands at any level. A separate history is maintained in debugging mode. To see the special commands available at the debug prompt, type ? and hit return. idebug {echo ?id?} ?args? Behaves just like echo, but only triggers when idebug is on. You can specify an optional id to further restrict triggering. If no id is specified, it defaults to the name of the command in which the call was made. idebug id ?id? Query or set the idebug id. This id is used by other idebug methods to determine if they should trigger or not. The idebug id can be a glob pattern and defaults to *. idebug off Turns idebug off. idebug on ?id? Turns idebug on. If id is specified, it sets the id to it. idebug {puts ?id?} args Behaves just like puts, but only triggers when idebug is on. You can specify an optional id to further restrict triggering. If no id is specified, it defaults to the name of the command in which the call was made. idebug show type ?level? ?VERBOSE? type must be one of vars, locals or globals. This method will output the variables/locals/globals present in a particular level. If VERBOSE is added, then it actually dumps out the values as well. level defaults to the level in which this method was called. idebug trace ?level? Prints out the stack trace from the specified level up to the top level. level defaults to the current level. SEE ALSO
dump(n), observe(n), tkcon(1), tkcon(n), tkconrc(5) KEYWORDS
Tk, console, debug COPYRIGHT
Copyright (c) Jeffrey Hobbs <jeff at hobbs.org> TkCon 2.5 idebug(n)