User forums > Nightly builds
The 18 June 2006 build is out.
MortenMacFly:
--- Quote from: royalbox on June 19, 2006, 02:31:44 am ---I still get access violations.
Are any of the devs looking into this?
--- End quote ---
Well, without a crash report or clear steps to reproduce how should the devs take care? For me C::B simply works - I cannot reproduce this issue. Could you try to compile C::B yourself to see if it's a nightly issue? That would really help.
With regards, Morten.
MortenMacFly:
--- Quote from: oz on June 19, 2006, 03:15:46 am ---did you log in as the system administrator or do you have the privilege to fully control the system? I *guess* that may be the problem.
--- End quote ---
I'm running Windows always in restricted (non-admin) mode. Here it works. I would wonder if access limitation were the reason for such crashes... but who knows? ;-)
With regards, Morten.
oz:
--- Quote from: MortenMacFly on June 19, 2006, 09:04:14 am ---
--- Quote from: oz on June 19, 2006, 03:15:46 am ---did you log in as the system administrator or do you have the privilege to fully control the system? I *guess* that may be the problem.
--- End quote ---
I'm running Windows always in restricted (non-admin) mode. Here it works. I would wonder if access limitation were the reason for such crashes... but who knows? ;-)
With regards, Morten.
--- End quote ---
Yes, hopefully that is the problem, because if I changed a computer lab at school, it never happened any more, same as some personal labtops. it only happens in one lab. but unfortunately, it really does not generate any report, because C::B will not crash. as I said, it keep working as normal, only the window will pop up again and again. right, I will show you the picture next time 8)
here it is! and the folder cb-crash-recover is empty.
[attachment deleted by admin]
royalbox:
--- Quote ---did you log in as the system administrator or do you have the privilege to fully control the system? I *guess* that may be the problem.
--- End quote ---
It's my own machine and I only run as administator.
--- Quote ---Well, without a crash report or clear steps to reproduce how should the devs take care?
--- End quote ---
Tell me where the crash report is and I'll post it. Clear steps to reproduce? I'm sorry, but I don't see how my post could have been any clearer bar adding pictures. Please tell me which steps you didn't understand and I'll try again.
I appreciate you're all working on this for free and for the fun of it, but clearly something is wrong when more than one person has the same problem.
thomas:
--- Quote ---here it is!
--- End quote ---
This screenshot is not very useful since it does not tell an awful lot.
The primary purpose of the crash handler is to allow you avoid a crash and to do a graceful shutdown and to preserve as much data as possible, in defiance of any real occurring crashes.
Nothing sucks as bad as losing your work if you haven't saved for an hour and you encounter a crash.
If you press "Abort", the crash handler will simply return control to the system exception handler (reading what's displayed in the message helps), so after you do that, the application *will* crash.
If you click on "Ignore", the crash handler will increment EP before returning control, this will in most cases cause the program to continue "just normal", but it will of course not write out a RPT.
It is generally still recommended that you save your work and close the application, even if everything seems to be "normal" afterwards, as you really cannot have a clue what internal effects the crash might have had.
--- Quote ---and the folder cb-crash-recover is empty.
--- End quote ---
I have not had a crash in many weeks now, but when I initially wrote this crash handler, it worked reliably. The code that's writing the backup copies has not been changed since then. All that was changed is that the crash handler is now generally enabled in the nightly builds thanks to dynamic linkage (which it was not before).
If the crash recovery folder is empty, then you probably did not have any documents open.
Administrator or not should not matter for writing out the backups, since it writes to your "MyFiles" folder -- unless something is horribly screwed up, you always have access to that location.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version