Sorry, when i pressed "send bug report", nothing
happened, so i'm posting it here.
Aside from the real bug report here, I'd like to note that
the build-priority setting in the project options window
does absolutely nothing - I can't get it to change the
order of compilation at all, neither in this version
(4.9.9.2) nor in version 4.9.9.0.
I set the option as follows:
With more than one *.cpp file in a project, I exclude
the "include" statements of these files to prevent double
definitions. I then make sure all files are marked
as "include in compilation" and "include in linking" in the
project options dialog. I then change the build priorities
of each file and click 'OK'. It has no effect. They stay in
whatever order they were initially.
Am I missing out on some really important step?
My e-mail address is killabunny@seductive.com, but I'll
be available on this forum.
Here's the real bug report:
Application version: 4.9.9.2
Platform : Windows 95 and later
OS version : version 4.10 (build 67766446)
Additional info: A
The following error occured in version 4.9.9.2:
Access violation at address 005871C1 in
module 'DEVCPP.EXE'. Read of address FFFFFFFF (at
address 0x005871C1)
Please include a description of what you were doing
before the error occured (please give as much precisions
as possible) :
I was Editing the build-priority setting in the project
options window. I've noticed that the build priority
settings didn't take any effect whatsoever; I've noticed
this effect with all projects i've made on this machine in
both version 4.9.9.0 and 4.9.9.2.
I changed the priorities to totally random values to see
the effect it had (and to try reproducing this bug).
Upon clicking 'ok' in the project options window, the
program crashed. I noticed this happens randomly, I
can't specify exactly what I did to make it crash - but
I'll keep looking. Another strange behavior is that it
occasionally closes several file windows when i click "ok"
in the project options after changing build priorities.
State information follows:
Stack trace:
0058F80A (0018E80A): ShowExceptionInfo
(ExceptionsAnalyzer - 566)
0058F9FF (0018E9FF):
TExceptionsAnalyzer.GlobalExceptionHandler
(ExceptionsAnalyzer - 574)
005871C1 (001861C1): TEditor.GetModified (editor - 418)
004E5436 (000E4436):
TSynBaseCompletionProposalForm.Notification
(SynCompletionProposal - 2212)
005871C1 (001861C1): TEditor.GetModified (editor - 418)
005871C1 (001861C1): TEditor.GetModified (editor - 418)
00572952 (00171952): TProjUnit.GetDirty (project - 367)
0057298C (0017198C): TProjUnit.Assign (project - 383)
0057A025 (00179025): TProject.SortUnitsByPriority
(project - 2008)
00578CCE (00177CCE): TProject.ShowOptions (project -
1679)
00559E2E (00158E2E):
TMainForm.actProjectOptionsExecute (main - 3551)
0059105B (0019005B): (devcpp - 230)
00591079 (00190079): (devcpp - 230)
Logged In: NO
correction: i think i found out how to reproduce it:
File -> new -> project, start a new project. Create two new .cpp files in it (or add them from existing files), and most
importantly* open them both for editing, and keep them open.
Goto project options and change their build priorities to
anything (eg. 1003 and 995 anything that swaps the order of
their builds so dev-c++ has to resort them), click OK. You
may notice one of the editor windows close, then without
touching anything try closing dev-c++ and it should crash.
Atleast thats what happens with me.