[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::debug

Title:DEBUG
Notice:Updated locations for reporting QARs -- see note 834.1
Moderator:LOWFAT::DIETER
Created:Fri Jan 24 1986
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1868
Total number of notes:8200

1855.0. "decwin callback/set break problem" by CSC32::J_HENSON (Don't get even, get ahead!) Wed Apr 09 1997 12:19

OpenVMS/Alpha V7.1, Dec C V5.5-002, Motif V1.2-4, debug V7.1

I am posting this just to see if it sounds familiar to anyone.  I only
have a customer's description of the problem.

My customer is reporting a problem with the debugger.  He is doing
the following.

 - using decwindows version of the debugger
 - his program uses decwindows calls (don't know which one) to establish
   a callback routine.
 - sets a break on the callback routine.
 - activates the callback by using a cascade button (I'm a bit shakey
   on this part.  However, the customer did state that this only seems
   to happen when he uses the cascade button).
 - gets the break.
 - nothing works after the break.  He can't switch windows, change the
   debugger 'input focus', run the program, or anything.  The only
   thing he can do is log in to another session and kill the debug
   session.

I know that this is a pretty sketchy problem statement, but I wanted to
go ahead and post what I know in hopes that I might get lucky.

If none of this sounds familiar, I'll try to get more info.  Is there
anything in particular (other than a reproducer) that I should ask for?

Thanks,

Jerry
T.RTitleUserPersonal
Name
DateLines
1855.1LOWFAT::DIETERWed Apr 09 1997 13:2626
Hi Jerry -

Here is a release note from the Dragon (V6.0?) release notes
(simply because that is what I have on hand):

>DECwindows Motif Interface Restrictions and Problems
>
>	The following problems or restrictions are specific to the
>	DECwindows Motif interface:
>
>...
>	* If you are stopped at a breakpoint, in a routine which has
>	  gotten control of the mouse pointer via a PointerGrab or a
>	  KeyboardGrab, you will hang your worksation.  
>
>	  To work around this problem, debug your program using two 
>	  workstations.  For more information, see the OpenVMS Debugger
>	  Manual.

As of V7.0 (I think, but certainly V7.1) we have been trying to move
the permanent restictions (such as the one above) into the manual, so
if you/he is using a recent version of the debugger, you will probably 
have to look through the manual to find this same information.

Mary