🚀 go-pugleaf

On Thu, 12 Jul 2007 15:16:46 +0200, Zara <me_zara@dea.spamcon.org>
wrote:

>On Thu, 12 Jul 2007 04:09:43 -0700, Antony Corbett
><a.corbett@celcat.com> wrote:
>
>>Has anyone else experienced access violations when running code that
>>has been "Optimized for Speed" (the default RELEASE setting)? Here's
>>the simplest example:
>>
>>1. Create a new VCL forms app
>>
>>2. Drop a TComboBox and TDateTimePicker on the main form
>>
>>3. Main form code:
>>
>>__fastcall TForm1::TForm1(TComponent* Owner)
>>	: TForm(Owner)
>>{
>>ComboBox1->Items->Add("Item1");
>>ComboBox1->OnChange = ComboBox1Change;
>>}
>>
>>void __fastcall TForm1::ComboBox1Change(TObject *Sender)
>>{
>>DateTimePicker1->Date = Now();
>>}
>>
>>4. Build using the RELEASE configuration (or any other configuration
>>with "Optimize for Speed" enabled)
>>
>>Now when you run the app and select "Item1" you get an access
>>violation. This happens using other constructs also, but the above is
>>the simplest example I could devise.
>>
>>Rgds
>>Antony
>
>
>I may be related to the bug I reported in QC 48623. I will try to take
>a llok at it tomorrow.
>
>Regards,
>
>Zara


I am able to tell you that it is exactly the same issue I reported in
QC 48623.

You should avoid Speed and Size optimizations, although Selected
Optimizations are OK.

Please, visit the report I made, make any commnet you see fit and vote
for it if you want it to be solved faster... it was reported on July
6th and no one has yet tracked it!

Regards,

zara