Author | Topic: Debug may wipe entire program! | |
---|---|---|
Itai Ben-Artzi | Debug may wipe entire program! on Sat, 28 Feb 2015 19:51:33 -0800 DO NOT DEBUG WITHOUT BACKUP OF YOUR PRG!!! While debugging, I’ve received the attached massages, the entire PRG was wiped and reduced to 0 bytes. Three times the workbench was frozen and twice I was able to quit, but lost the entire PRG. The conditions created this (to the best of my recollection): down-line the ALTD(), error occurred or a msgbox() displayed. -Itai DO NOT DEBUG WITHOUT BACKUP OF YOUR PRG.docx | |
Jan Escholt | Re: Debug may wipe entire program! on Sun, 01 Mar 2015 07:45:06 +0100 Itai, I had this several times with the VX, but never with the workbench. Jan Am 01.03.2015 um 04:51 schrieb "Itai Ben-Artzi": > DO NOT DEBUG WITHOUT BACKUP OF YOUR PRG!!! > > While debugging, I’ve received the attached massages, the entire PRG was > wiped and reduced to 0 bytes. Three times the workbench was frozen and > twice I was able to quit, but lost the entire PRG. > > The conditions created this (to the best of my recollection): down-line > the ALTD(), error occurred or a msgbox() displayed. > > > > > -Itai | |
Itai Ben-Artzi | Re: Debug may wipe entire program! on Sun, 01 Mar 2015 13:01:09 -0800 Interestingly, I’ve never had it with VX, but 5 times with the new workbench. BTW, what is the different between “workbench” and “workbench (admin)”? -Itai | |
Jonathan Leeming | Re: Debug may wipe entire program! on Sun, 01 Mar 2015 17:20:25 -0700 On Sun, 01 Mar 2015 13:01:09 -0800, Itai Ben-Artzi wrote: >Interestingly, Ive never had it with VX, but 5 times with the new >workbench. >BTW, what is the different between workbench and workbench (admin)? >-Itai Hi Itai, According to Alaska's documentation it is a rights issue ... Note: There are two ways to open up the Workbench from your Start menu: via the items "Xbase++ Workbench" and "Xbase++ Workbench (Admin)". The latter menu item runs the IDE using elevated privileges. This is the recommended mode for working with CXP, because the document root folder of most web servers is write-protected for normal users. The admin variation runs xwb.exe with the parameter -ee. Regards... Jonathan | |
Till Warweg | Re: Debug may wipe entire program! on Mon, 02 Mar 2015 15:27:36 +0100 Itai, This is bad! Obviously, corruptions such as the one you're describing should never happen! Could you please explain what you meant by "down-line the ALTD()"? Was it always the same .PRG and/or code section that you were debugging at the time of the crash? Were you asked whether you wanted to save changes or was it rather a "poof" kind of crash? Regards, Till Warweg [Alaska Software] -------------------------------------------------------------------- Technical Support: support@alaska-software.com News Server: news.alaska-software.com Homepage: http://www.alaska-software.com KnowledgeBase: http://www.alaska-software.com/kb -------------------------------------------------------------------- "Itai Ben-Artzi" schrieb im Newsbeitrag news:724e57e0$2a6aeb68$25341f@news.alaska-software.com... > DO NOT DEBUG WITHOUT BACKUP OF YOUR PRG!!! > > While debugging, I’ve received the attached massages, the entire PRG was > wiped and reduced to 0 bytes. Three times the workbench was frozen and > twice I was able to quit, but lost the entire PRG. > > The conditions created this (to the best of my recollection): down-line the > ALTD(), error occurred or a msgbox() displayed. > > > > > -Itai > | |
Itai Ben-Artzi | Re: Debug may wipe entire program! on Mon, 02 Mar 2015 11:18:28 -0800 Till, I’ve simply place the ALTD() where I want to start the debug. A few lines below I have MsgBox(). When the execution of code reached that (msgbox) line, the German messages popped-up and the PRG has been overwritten with 0 bites. On other occasions it happened when an error message (from my error class) popped-up, or when I’ve pressed F9 to complete the execution of the specific procedure. I hope this help. -Itai |