×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Log off, or reclaim your activation group if applicable... Recompiling a program with replace option doesn't change an already activated module... I expect that if you did SysReq 3, and reviewed your call stack, it would show your program object in QRPLOBJ library...
-Eric DeLong
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Therrien
Sent: Tuesday, November 20, 2012 2:30 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] RDP 8.5 and Service Entry points - reset of a program/debug
How do you get RDP Service Entry points to reset/restart once a program has been recompiled?
I have had a gnawing issue for a while...
1. Set a service entry point on a program
2. Run the program
3. Debug in RDP thanks to the service entry point until logic error is determined
4. Find code that needs to be changed and fix it.
5. Recompile the program
6. Refresh the service entry point (or even delete the service entry point and reset it)
7. Run the newly compiled version of the program
8. However ... I no longer can get the RDP debugger to kick in on the service entry point.
In this scenario, the only way I have been able to get the service entry point debugging to work is exit RDP and restart.
There must be a better way.
Can anyone have any offer any tips for this?
Paul Therrien
Orion South, Inc.
504-374-9551
800-437-7173; Ext. 551
ptherrien@xxxxxxxxxxxxxxx<mailto:ptherrien@xxxxxxxxxxxxxxx>
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: RDP 8.5 and Service Entry points - reset of a program/debug, (continued)
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
