🚀 go-pugleaf

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
>
>