Crash after leaving TC 10.0.0.69
- Thread starter Lippolt
- Start date
Crash after leaving TCC 10.0.0.69
On Sat, 11 Jul 2009 11:11:35 -0500, Lippolt <> wrote:
|I get a crash after leaving TCC, reproducable.
|
|10.0.0.68 was OK.
|
|WinXP, German language.
Same here; language = English. Whenever I close TCC 10.0.0.69, it crashes. I
hope it's fixed very quickly!
--
- Vince
On Sat, 11 Jul 2009 11:11:35 -0500, Lippolt <> wrote:
|I get a crash after leaving TCC, reproducable.
|
|10.0.0.68 was OK.
|
|WinXP, German language.
Same here; language = English. Whenever I close TCC 10.0.0.69, it crashes. I
hope it's fixed very quickly!
--
- Vince
Apparently, according to WinDbg, it's doing something naughty after ExitProcess is called. It will break on ExitProcess (no violation). But later,
Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=00000000 ebx=0000ffff ecx=ffffffff edx=00d8db10 esi=1020d000 edi=8ca4435c
eip=7c901240 esp=00d8daf8 ebp=00d8db18 iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
ntdll!RtlInitString+0x1b:
7c901240 f2ae repne scas byte ptr es:[edi]
ntdll!RtlInitString+0x1b
WARNING: Stack unwind information not available. Following frames may be wrong.
TakeCmd!aIniFile+0x14aa3b
TakeCmd!aIniFile+0x25cb10
ntdll!LdrpCallInitRoutine+0x14
ntdll!LdrShutdownProcess+0x14f
kernel32!_ExitProcess+0x42
kernel32!ExitProcess+0x14
TakeCmd!Do_Cmd+0x3db8
TakeCmd!Do_Cmd+0x3fa5
TakeCmd!Do_Cmd+0x3fce
TakeCmd!Exit_Cmd+0xb6
TakeCmd!Command+0x931
TakeCmd!Command+0x6d1
TakeCmd!GetLine+0x46
image00400000+0x1740
0xd8ff60
Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=00000000 ebx=0000ffff ecx=ffffffff edx=00d8db10 esi=1020d000 edi=8ca4435c
eip=7c901240 esp=00d8daf8 ebp=00d8db18 iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
ntdll!RtlInitString+0x1b:
7c901240 f2ae repne scas byte ptr es:[edi]
ntdll!RtlInitString+0x1b
WARNING: Stack unwind information not available. Following frames may be wrong.
TakeCmd!aIniFile+0x14aa3b
TakeCmd!aIniFile+0x25cb10
ntdll!LdrpCallInitRoutine+0x14
ntdll!LdrShutdownProcess+0x14f
kernel32!_ExitProcess+0x42
kernel32!ExitProcess+0x14
TakeCmd!Do_Cmd+0x3db8
TakeCmd!Do_Cmd+0x3fa5
TakeCmd!Do_Cmd+0x3fce
TakeCmd!Exit_Cmd+0xb6
TakeCmd!Command+0x931
TakeCmd!Command+0x6d1
TakeCmd!GetLine+0x46
image00400000+0x1740
0xd8ff60
Crash after leaving TCC 10.0.0.69
Lippolt wrote:
I've removed build 69, changed the version number, rebuilt everything
(nothing else changed), turned off the web and ftp sites to prevent the
same thing happening, uploaded build 70, and turned everything back on.
Let me know if you have any problems with build 70.
(It would be safer to wait until I announce a new build before
downloading it!)
Rex Conn
JP Software
Lippolt wrote:
You grabbed 10.0.69 before I was finished uploading everything.
I've removed build 69, changed the version number, rebuilt everything
(nothing else changed), turned off the web and ftp sites to prevent the
same thing happening, uploaded build 70, and turned everything back on.
Let me know if you have any problems with build 70.
(It would be safer to wait until I announce a new build before
downloading it!)
Rex Conn
JP Software
Crash after leaving TCC 10.0.0.69
On Sat, 11 Jul 2009 13:45:31 -0500, rconn <> wrote:
|Let me know if you have any problems with build 70.
No more crash on exit.
--
- Vince
On Sat, 11 Jul 2009 13:45:31 -0500, rconn <> wrote:
|Let me know if you have any problems with build 70.
No more crash on exit.
--
- Vince
Re: Crash after leaving TCC 10.0.0.69
Thank you very much for the fast fix.
I found the new version by the update check performed at program start, not by the announcement on the web page.
Best regards from Hannover, Germany
Peter
No crash after exit with version 10.0.0.70.
Thank you very much for the fast fix.
I found the new version by the update check performed at program start, not by the announcement on the web page.
Best regards from Hannover, Germany
Peter