🚀 go-pugleaf

In article <4810b531$1@newsgroups.borland.com>,
 "roladdon" <roladdon@PutMyServerHere.ca> wrote:

> When I do F9 (run)  in any project - I usually get an error "access 
> violation at....  "

   What happens when you run it outside of the IDE?
-- 
David Dean (CodeGear)
Lead C++ QA Engineer

It runs fine outside the IDE
I am able to influence the run probability by changing the priority of the 
bds.exe task
and by setting the processor affinity of the  bds.exe task

Reducing the priority of the  bds.exe task by one level helped but
the best success I had was with:
    Task manager -> bds.exe   set affinity to use CPU 0  only

Now it will run about 9 times out of 10
But earlier it was 4 times out of 5

And yes - the error still happens.
thanks,
Roland



"David Dean [CodeGear]" <david.dean.no@spam.codegear.com> wrote in message 
news:david.dean.no-7360C5.12241024042008@h10s143a100n47.user.nortelnetworks.com...
> In article <4810b531$1@newsgroups.borland.com>,
> "roladdon" <roladdon@PutMyServerHere.ca> wrote:
>
>> When I do F9 (run)  in any project - I usually get an error "access
>> violation at....  "
>
>   What happens when you run it outside of the IDE?
> -- 
> David Dean (CodeGear)
> Lead C++ QA Engineer 

roladdon wrote:
> 
> Now it will run about 9 times out of 10
> But earlier it was 4 times out of 5
> 
> And yes - the error still happens.

You are, almost certainly, using an uninitialized variable somewhere in 
your code. The behavior depends upon the previous value stored in that 
location. Some values lead to an AV some don't, hence the random 
behavior you are seeming.

Dennis Cote

I open CBuilder2007
File->New->VCL Forms Application
F9 (run)
that's where it happens

Sometimes it stops at the CPU window:
(always at a   jmp $00....)
and pressing F9 another time will give the AV error

Sometimes it will go straight to the AV error

Roland 

roladdon wrote:
> I open CBuilder2007
> File->New->VCL Forms Application
> F9 (run)

At which point it starts executing your application's code.

You can try putting a breakpoint at the beginning of your application's 
WinMain function and see if it gets that far. If it does, then you can 
step through the initialization until you pass the routine that triggers 
the error. If not, it may be that the error occurs during the 
initialization of globals or static members which happens before WinMain 
is called.

> that's where it happens
> 
> Sometimes it stops at the CPU window:
> (always at a   jmp $00....)
> and pressing F9 another time will give the AV error

What is on the call stack at that point?

> 
> Sometimes it will go straight to the AV error

When you say AV error, do you mean an AV exception that is caught by the 
debugger, or an AV error in the bds.exe that is caught by the OS?

Dennis Cote

It does not get to WinMain()
It always stops at different points - please see below the two example event 
logs

Roland
___________________________________________________________
1)
Thread Start: Thread ID: 8496. Process Project1.exe (9844)
Process Start: C:\Documents and Settings\Roland\My Documents\RAD 
Studio\Projects\Debug\Project1.exe. Base Address: $00400000. Process 
Project1.exe (9844)
Module Load: Project1.exe. Has Debug Info. Base Address: $00400000. Process 
Project1.exe (9844)
Module Load: ntdll.dll. No Debug Info. Base Address: $7C900000. Process 
Project1.exe (9844)
Module Load: KERNEL32.dll. No Debug Info. Base Address: $7C800000. Process 
Project1.exe (9844)
Thread Start: Thread ID: 9184. Process Project1.exe (9844)
Module Load: vcl100.bpl. No Debug Info. Base Address: $200E0000. Process 
Project1.exe (9844)
Module Load: LVPrcInj.dll. No Debug Info. Base Address: $00800000. Process 
Project1.exe (9844)

2)
Thread Start: Thread ID: 8940. Process Project1.exe (8264)
Process Start: C:\Documents and Settings\Roland\My Documents\RAD 
Studio\Projects\Debug\Project1.exe. Base Address: $00400000. Process 
Project1.exe (8264)
Module Load: Project1.exe. Has Debug Info. Base Address: $00400000. Process 
Project1.exe (8264)
Module Load: ntdll.dll. No Debug Info. Base Address: $7C900000. Process 
Project1.exe (8264)
Module Load: KERNEL32.dll. No Debug Info. Base Address: $7C800000. Process 
Project1.exe (8264)
Module Load: vcl100.bpl. No Debug Info. Base Address: $200E0000. Process 
Project1.exe (8264)
Thread Start: Thread ID: 9812. Process Project1.exe (8264)
Module Load: rtl100.bpl. No Debug Info. Base Address: $20000000. Process 
Project1.exe (8264)





"Dennis Cote" <denniscote@gmail.com> wrote in message 
news:4810f4a5$1@newsgroups.borland.com...
> roladdon wrote:
>> I open CBuilder2007
>> File->New->VCL Forms Application
>> F9 (run)
>
> At which point it starts executing your application's code.
>
> You can try putting a breakpoint at the beginning of your application's 
> WinMain function and see if it gets that far. If it does, then you can 
> step through the initialization until you pass the routine that triggers 
> the error. If not, it may be that the error occurs during the 
> initialization of globals or static members which happens before WinMain 
> is called.
>
>> that's where it happens
>>
>> Sometimes it stops at the CPU window:
>> (always at a   jmp $00....)
>> and pressing F9 another time will give the AV error
>
> What is on the call stack at that point?
>
>>
>> Sometimes it will go straight to the AV error
>
> When you say AV error, do you mean an AV exception that is caught by the 
> debugger, or an AV error in the bds.exe that is caught by the OS?
>
> Dennis Cote
>
> 

I forgot to say - the Caption of the AV error says always "Debugger Fault 
notification"

Re.: "What is on the call stack at that point?"

different things - many times  "Dlgs"

nothing - when it pops up the Debugger Fault notification up right away with 
the AV error, when I click OK
call stack contains "ntdll.RtlInitUnicodeString + 0x1b"

Roland