PellesC crashes as it starts.

[tima]

The program starts (I can open it with or without a file), and generates an error message right away:

If I open a file with the program, I can see the code, but it crashes all the same.

I reinstalled the program, but it didn't help.

Can anyone help?

Thanks, tima.

[frankie]

This problem seems related to your PC and OS.
Which erro message you get when the program starts?
Which OS, and eventually which service pack are you using?
You can see the code then it crashes? When happen? when trying to compile the code?
You must supply more info's to get help.

[tima]

This problem seems related to your PC and OS.
Which erro message you get when the program starts?
Which OS, and eventually which service pack are you using?
You can see the code then it crashes? When happen? when trying to compile the code?
You must supply more info's to get help.

I believe I did. I put a BIG picture in the post showing the error message.
I'm using Windows XP, service pack2.

As I said, it crashes right when I open the program. The code opens, but it immediately gives the error and closes.

[Synfire]

Tima,

From your picture PoIDE is most likely trying to access a file, socket, or registry that it doesn't have access too. The C0000008h error is most commonly caused when one attempts to read from or write to invalid handles. You said you reinstalled; Did you do a clean reinstall (eg you deleted all registry keys and uninstalled PellesC before reinstalling) or did you overwrite (eg install on top of the corrupted version)? Try doing a clean install if you haven't. Also, you might try running PoIDE as administrator and seeing if it works. If it does, then it's possible that your current user's privilages don't allow you access to parts of the system or registry that PoIDE is trying to access. I do believe there should be a bit of error checking in PoIDE to alert against such errors, but it's common for developers to overlook one or two spots. You might have found one but I would check your systems configuration and user privilages as that's most likely the primary cause of the error.

I do agree with frankie that you need to supply more information if you plan to get any decent help. For example, are you running any other software that could be interfering with PoIDE's operations such as preforming anti-virus scans (which could have registry and files locked while PoIDE is trying to access them) or file/registry monitoring software. For best support you could get a copy of OllyDBG and install it for JIT Debugging, then run PoIDE. When it crashes you will get a disassembly of the 7C964ED1h address and surrounding opcodes as well as what the registers contain, the stack, etc. A screenshot of that would give members more than enough information to disect the problem in detail and give you a complete answer.

frankie,

Why was this topic moved out of the Bug reports section and into the Beginners section? Not to question the staff or anything but this would be considered a bug report.

Regards,
Bryant Keller

[tima]

Tima,

You said you reinstalled; Did you do a clean reinstall or did you overwrite? Try doing a clean install if you haven't. Also, you might try running PoIDE as administrator and seeing if it works. If it does, then it's possible that your current user's privilages don't allow you access to parts of the system or registry that PoIDE is trying to access. I do believe there should be a bit of error checking in PoIDE to alert against such errors, but it's common for developers to overlook one or two spots. You might have found one but I would check your systems configuration and user privilages as that's most likely the primary cause of the error.

I do agree with frankie that you need to supply more information if you plan to get any decent help. For example, are you running any other software that could be interfering with PoIDE's operations such as preforming anti-virus scans (which could have registry and files locked while PoIDE is trying to access them) or file/registry monitoring software. For best support you could get a copy of OllyDBG and install it for JIT Debugging, then run PoIDE. When it crashes you will get a disassembly of the 7C964ED1h address and surrounding opcodes as well as what the registers contain, the stack, etc. A screenshot of that would give members more than enough information to disect the problem in detail and give you a complete answer.

frankie,

Why was this topic moved out of the Bug reports section and into the Beginners section? Not to question the staff or anything but this would be considered a bug report.

Regards,
Bryant Keller

I did a clean reinstall. I uninstalled PellesC, then installed it again. I didn't do anything else (I'm assuming it cleans the program's registry files, etc. Correct me if I'm wrong).

I am not running anything that might interfere with the program. Not even another compiler, or an antivirus.

The user I'm using is the administrator in this computer, so I don't think it could be that kind of problem.

I guess I'll go back to my old compiler - I found the problem it had, which was the reason I was looking for a new one (And PellesC looked good).

Thanks a lot for your help.
Tima.

P.S. Yeah, I had no idea why a crashing program is a beginner question. Never mind though.

[TimoVJL]

Can you open bare IDE ?
Can you open Tools Options from menu ?
Is there poide.xpt left behind poide.exe crash ?
What happens if you open poide.exe  with /n commandline option ?

[frankie]

Sorry if this seemed rude, my purpose was to try to keep in the bug section posts that were referred to real bugs. When someone have a problem may want to look in that section to identify a similar bug with the relative solution. Keeping a lot of not-appurated-bugs make, imo, inefficient the section.
I have read probably too fast the post and considered this report more related to the specific PC than to the PellesC compiling system.

[Synfire]

Tima,

I did a clean reinstall. I uninstalled PellesC, then installed it again. I didn't do anything else (I'm assuming it cleans the program's registry files, etc. Correct me if I'm wrong).

I am not running anything that might interfere with the program. Not even another compiler, or an antivirus.

The user I'm using is the administrator in this computer, so I don't think it could be that kind of problem.

The reason I'm refering to that is because the error message you are recieving is a generic message from Windows that occurs when an application attempts to access data from an invalid handle. Without being at your computer or seeing the code located at memory address 7C964ED1h there isn't much else we can do other than give you generic advice like above.

I guess I'll go back to my old compiler - I found the problem it had, which was the reason I was looking for a new one (And PellesC looked good).

Thanks a lot for your help.
Tima.

P.S. Yeah, I had no idea why a crashing program is a beginner question. Never mind though.

I'm sorry this experience has turned you off to PellesC, it really is a great utility. Hopefully it hasn't discouraged you from giving it another try in the future.

frankie,

Sorry if this seemed rude, my purpose was to try to keep in the bug section posts that were referred to real bugs. When someone have a problem may want to look in that section to identify a similar bug with the relative solution. Keeping a lot of not-appurated-bugs make, imo, inefficient the section.
I have read probably too fast the post and considered this report more related to the specific PC than to the PellesC compiling system.

Well, I can understand that. But wouldn't it be better to make a sub-section in the Bug Reports forum for "real bugs" (known bugs, etc.) and let users continue to report their findings in the base Bug Reports forum? I mean, from a users point of view, when you come a cross a bug your first instinct would be to post in the Bug Reports forum not the other forums. It just seems like it would save you time in the long run.

[PauloH]

Hello friend.

I had problems like you, but not with Pelles C. The solution: reinstall the OS, formatting the whole HD. The cause: virus, rootkit and other malefic eletronic 'creatures'... (he he he).
(Forgive my poor english!)
Bye,
Paulo H.

[Phil]

I've the same problem as you on a Windows XP-SP2 system with Pelles C 4.50. The problem comes from Pelles C itself (since version 4.50) in the WizAddProjectFileA module and not from Windows. With the previous version of Pelles C (4.0), there is no problem.

Here some additional informations obtained with the Microsoft Windows Debugger:

ModLoad: 5ad70000 5ada8000   C:\WINDOWS\system32\UxTheme.dll
ModLoad: 10000000 1002c000   C:\Program Files\PellesC\Bin\Intl\rsrc0009.dll
ModLoad: 77c00000 77c08000   C:\WINDOWS\system32\VERSION.dll
ModLoad: 03c90000 03cc0000   C:\PROGRA~1\BABYLO~1\CAPTLIB.DLL
ModLoad: 732e0000 732e5000   C:\WINDOWS\system32\riched32.dll
ModLoad: 74e30000 74e9c000   C:\WINDOWS\system32\RICHED20.dll
ModLoad: 040e0000 040f1000   C:\Program Files\PellesC\Bin\Wizards\conapp.dll
ModLoad: 040e0000 040f6000   C:\Program Files\PellesC\Bin\Wizards\custcntl.dll
ModLoad: 040e0000 040f7000   C:\Program Files\PellesC\Bin\Wizards\msvcproj.dll
ModLoad: 040e0000 040f6000   C:\Program Files\PellesC\Bin\Wizards\winapp.dll
ModLoad: 040e0000 040f4000   C:\Program Files\PellesC\Bin\Wizards\windll.dll
(c58.b2c): Invalid handle - code c0000008 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=c0000008 ebx=01ace0c4 ecx=043bff68 edx=7c90eb3d esi=00000000 edi=00000001
eip=7c90eb74 esp=043bff14 ebp=043bff64 iopl=0         nv up ei pl nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000206
ntdll!KiRaiseUserExceptionDispatcher+0x37:
7c90eb74 8b0424           mov     eax,[esp]         ss:0023:043bff14=c0000008
   ______________________________________________________________________

Call stack:
   043bff64 7c90eb94 ntdll!KiRaiseUserExceptionDispatcher+0x37
   043bff78 004aee77 ntdll!KiFastSystemCallRet
   043bffb4 7c80b683 poide!WizAddProjectFileA+0xa02c7
   043bffec 00000000 kernel32!GetModuleFileNameA+0x1b4
   ______________________________________________________________________

ntdll!KiRaiseUserExceptionDispatcher:
7c90eb3d 55               push    ebp
7c90eb3e 8bec             mov     ebp,esp
7c90eb40 83ec50           sub     esp,0x50
7c90eb43 8944240c         mov     [esp+0xc],eax
7c90eb47 64a118000000     mov     eax,fs:[00000018]
7c90eb4d 8b80a4010000     mov     eax,[eax+0x1a4]
7c90eb53 890424           mov     [esp],eax
7c90eb56 c744240400000000 mov     dword ptr [esp+0x4],0x0
7c90eb5e c744240800000000 mov     dword ptr [esp+0x8],0x0
7c90eb66 c744241000000000 mov     dword ptr [esp+0x10],0x0
7c90eb6e 54               push    esp
7c90eb6f e838000000       call    ntdll!RtlRaiseException (7c90ebac)
7c90eb74 8b0424           mov     eax,[esp]         ss:0023:043bff14=c0000008
7c90eb77 8be5             mov     esp,ebp
7c90eb79 5d               pop     ebp
7c90eb7a c3               ret
7c90eb7b 90               nop
7c90eb7c 8da42400000000   lea     esp,[esp]
7c90eb83 8d4900           lea     ecx,[ecx]
7c90eb86 90               nop
7c90eb87 90               nop
7c90eb88 90               nop
7c90eb89 90               nop
7c90eb8a 90               nop
ntdll!KiFastSystemCall:
7c90eb8b 8bd4             mov     edx,esp
   ______________________________________________________________________

7c80b64c 6a10             push    0x10
7c80b64e 6890b6807c       push    0x7c80b690
7c80b653 e86e6effff       call    kernel32!ReleaseMutex+0x1f (7c8024c6)
7c80b658 8365fc00         and     dword ptr [ebp-0x4],0x0
7c80b65c 64a118000000     mov     eax,fs:[00000018]
7c80b662 8945e0           mov     [ebp-0x20],eax
7c80b665 817810001e0000   cmp     dword ptr [eax+0x10],0x1e00
7c80b66c 750f             jnz    kernel32!GetModuleFileNameA+0x1ae (7c80b67d)
7c80b66e 803d0840887c00 cmp byte ptr [kernel32!SetConsoleMaximumWindowSize+0x4dc6 (7c884008)],0x0
7c80b675 7506             jnz    kernel32!GetModuleFileNameA+0x1ae (7c80b67d)
7c80b677 ff15e812807c     call    dword ptr [kernel32+0x12e8 (7c8012e8)]
7c80b67d ff750c           push    dword ptr [ebp+0xc]
7c80b680 ff5508           call    dword ptr [ebp+0x8]
7c80b683 50               push    eax
7c80b684 e8cf090000       call    kernel32!ExitThread (7c80c058)
7c80b689 90               nop
7c80b68a 90               nop
7c80b68b 90               nop
7c80b68c 90               nop
7c80b68d 90               nop
7c80b68e 90               nop
7c80b68f 90               nop
7c80b690 ffff             
7c80b692 ffff             
7c80b694 10ab837c26ab     adc     [ebx+0xab267c83],ch
7c80b69a 837c909090       cmp     dword ptr [eax+edx*4-0x70],0xffffff90
7c80b69f 90               nop
   ______________________________________________________________________

[TimoVJL]

Are these computers using Hyper-Threading or Core Duo prosessor ?

[Phil]

Yes, this problem occurs on a PC with hyper-threading activated.

[TimoVJL]

If you remove register entries for PellesC (Pelle Orinius)
and rename C:\Program Files\PellesC\Bin\AddIns directory to something else
and start poide.exe with /n commanline option, does it start ?

If so, later you can test renaming directory back to AddIns

[Phil]

I've deactivated hyper-threading in the BIOS and now Pelles C is OK but my Windows XP sees only one CPU which is frustrating.

This seems to confirm there is a serious problem in poide.exe (and perhaps in other components of Pelles C) on multiprocessor systems.

[JohnF]

I've deactivated hyper-threading in the BIOS and now Pelles C is OK but my Windows XP sees only one CPU which is frustrating.

This seems to confirm there is a serious problem in poide.exe (and perhaps in other components of Pelles C) on multiprocessor systems.

What precautions does one need to take when programming for multiprocessors?

John