User forums > Nightly builds
The 18 June 2006 build is out.
royalbox:
Please tell me how to generate a crash report. If I click abort, a common dialog will open with the caption "open program". I saved a file to the desktop, but it was empty. Before CB closes it says that this file has been modified, save the changes? Whether I choose OK or Cancel, the file is empty. Please tell me how I can generate a crash report, thanks.
EDIT:
The dialog is just code::blocks continuing to carry out the 'open' command -- because it didn't abort. I assumed it was to save a crash report.
oz:
--- Quote from: thomas on June 19, 2006, 01:41:17 pm ---This screenshot is not very useful since it does not tell an awful lot.
--- End quote ---
yes, you are right :?
--- Quote ---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.
--- End quote ---
Every time I press 'Abort' two or three times to keep the program running, I am pretty sure here.
I forgot what happened when I pressed the other buttons, but I will try next time. Oh, I remebered it crashed once by choosing another option, certainly there is a crash report, but I cannot remeber clearly. I will post the report next time.
kkez:
--- Quote from: thomas on June 19, 2006, 01:41:17 pm ---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.
--- End quote ---
That's not true, after clicking two or three times on abort C::B doesn't crash.
BTW, i always get a crash handler dialogbox doing this:
1) File->Open...
2) create a new folder
3) insert a name and press enter
4) click 3 or 4 times on "Abort", C::B will continue to run
thomas:
--- Quote from: kkez on June 19, 2006, 02:44:16 pm ---
--- Quote from: thomas on June 19, 2006, 01:41:17 pm ---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.
--- End quote ---
That's not true, after clicking two or three times on abort C::B doesn't crash.
--- End quote ---
What makes you say that? First...
--- Code: ---switch(MessageBox(0, buf.c_str(), _T("Woah!"), MB_ABORTRETRYIGNORE))
{
case IDABORT:
return EXCEPTION_CONTINUE_SEARCH;
break;
--- End code ---
This gives control to the next handler. Unless you have installed a system-wide exception handler of your own, there is none other than the default handler left, which will show "The application has crashed..." and will terminate Code::Blocks.
And second...
royalbox:
--- Quote ---That's not true, after clicking two or three times on abort C::B doesn't crash.
What makes you say that?
--- End quote ---
I say this too, and the reason I say it, is because that is what happens. You click on abort and code::blocks carries on running.
--- Quote ---This gives control to the next handler. Unless you have installed a system-wide exception handler of your own, there is none other than the default handler left, which will show "The application has crashed..." and will terminate Code::Blocks.
--- End quote ---
See, the problem here is that you're looking at the code and saying it's not possible that code::blocks doesn't abort. Myself and the other posters are physically clicking abort and seeing that code::blocks doesn't abort. Either we're making it up or it is happening. I can't prove that I'm not making it up but I ask you to consider the possibility that I'm not, and perhaps we can work together to try and find the answer.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version