TC vanishes after launching the internal viewer by F3

The behaviour described in the bug report is either by design, or would be far too complex/time-consuming to be changed

Moderators: white, Hacker, petermad, Stefan2

Post Reply
prantlf
Junior Member
Junior Member
Posts: 3
Joined: 2009-08-19, 09:07 UTC

TC vanishes after launching the internal viewer by F3

Post by *prantlf »

Hi,

It started after updating to the RC1. It happens with any viewed file. I removed all plugins. No dialog comes up, the program exits silently. I turned off DEP for TOTALCMD.exe to be sure that OS was not killig it. Going back to the beta 8 did not fix it. It seems that something changed in my environment but I have no clue what it was.

Out of curiosity I downloaded the separate lister.exe (32-bit version) and it crashes too. Interesting.

I attached to the TOTALCMD process with VS and uploaded the minidump to .h.t.t.p. : // prantl.host.sk/tmp/TOTALCMD.dmp.zip .

Any idea why the internal lister started to misbehave?

OS: Windows XP SP3 32-bit.

Thank you,
Ferda
Top
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48088
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:
Contact ghisler(Author)

Post by *ghisler(Author) »

Thanks for the dump. Windbg tells me that the error occurs in SciLister.wlx plugin, so apparently you didn't completly remove all lister plugins:

Code: Select all

Microsoft (R) Windows Debugger  Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\test2\empty\TOTALCMD.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Windows XP Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
Debug session time: Wed Aug 19 11:30:00.000 2009 (GMT+2)
System Uptime: not available
Process Uptime: 0 days 0:02:36.000
Symbol search path is: srv*C:\SYMBOLS*http://msdl.microsoft.com/download/symbols
Executable search path is: 
.........................................
(898.298): Access violation - code c0000005 (!!! second chance !!!)
eax=ffff05ff ebx=00000000 ecx=00000000 edx=00000101 esi=017f10ce edi=00136134
eip=ffff05ff esp=001360d0 ebp=001360f8 iopl=0         nv up ei ng nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000286
ffff05ff ??               ???
0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** WARNING: Unable to verify timestamp for SciLister.wlx
*** ERROR: Module load completed but symbols could not be loaded for SciLister.wlx
*** WARNING: Unable to verify timestamp for TOTALCMD.EXE
*** ERROR: Module load completed but symbols could not be loaded for TOTALCMD.EXE

FAULTING_IP: 
+ffffffffffff05ff
ffff05ff ??               ???

EXCEPTION_RECORD:  ffffffff -- (.exr ffffffffffffffff)
ExceptionAddress: ffff05ff
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000008
   Parameter[1]: ffff05ff
Attempt to execute non-executable address ffff05ff

DEFAULT_BUCKET_ID:  CODE_RUNNING_ON_HEAP

PROCESS_NAME:  TOTALCMD.EXE

ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang  "%s" konnte nicht auf dem Speicher durchgef hrt werden.

WRITE_ADDRESS:  ffff05ff 

BUGCHECK_STR:  ACCESS_VIOLATION

IP_ON_HEAP: 
+ffffffffffff05ff
ffff05ff ??               ???

LAST_CONTROL_TRANSFER:  from 7e418734 to ffff05ff

STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
001360cc 7e418734 000f05b8 00000808 00000020 0xffff05ff
001360f8 7e418816 017f10ce 000f05b8 00000808 user32!InternalCallWinProc+0x28
00136160 7e428ea0 00000000 017f10ce 000f05b8 user32!UserCallWinProcCheckWow+0x150
001361b4 7e428eec 00a35b58 00000808 00000020 user32!DispatchClientMessage+0xa3
001361dc 7c90e473 001361ec 00000018 00a35b58 user32!__fnDWORD+0x24
00136200 7e4194be 7e42af42 000f05b8 00000808 ntdll!KiUserCallbackDispatcher+0x13
0013623c 7e42f40b 00a35b58 00000808 00000020 user32!NtUserMessageCall+0xc
0013625c 018094ff 000f05b8 00000808 00000020 user32!SendMessageA+0x7f
00136298 018067af 01385920 00000020 001362b8 SciLister+0x194ff
001363f8 017f10c3 01383fc0 017f183d 00000001 SciLister+0x167af
00136424 006032f2 00180626 001370e3 00000005 SciLister+0x10c3
0013657c 0060a5f2 00000000 00000000 00f05188 TOTALCMD+0x2032f2
00138770 00608b36 00138828 004156ac 001387c4 TOTALCMD+0x20a5f2
00138780 004156c6 0041775a 00138798 00417764 TOTALCMD+0x208b36
001387c4 00441ddb 00eb2f60 00138828 00efb48c TOTALCMD+0x156c6
0013881c 00441d19 00efb48c 0000b019 00000000 TOTALCMD+0x41ddb
00138838 00443c0d 00000000 0013f1b8 00443c17 TOTALCMD+0x41d19
00138864 00443c69 00efb48c 00444ea3 00efb48c TOTALCMD+0x43c0d
001388cc 00441d19 004158cc 0000b00b 00000000 TOTALCMD+0x43c69
001388e8 00441475 00000000 00000001 0013ccf0 TOTALCMD+0x41d19
00139120 004d3792 00139300 0013935c 00000000 TOTALCMD+0x41475
0013dd60 00512150 00000000 00000387 0050ee02 TOTALCMD+0xd3792
0013f1b0 00503eec 0013fcc0 005062f4 0013fc1c TOTALCMD+0x112150
0013fc1c 00444815 00000002 00000002 004447f0 TOTALCMD+0x103eec
0013fca4 004433b3 0013fcf0 00e8f5a0 00000000 TOTALCMD+0x44815
0013fcb8 00443d27 0013fccc 00443d4b 0013fce8 TOTALCMD+0x433b3
0013fce8 00413e8a 00000104 00000072 203d0001 TOTALCMD+0x43d27
0013fd00 7e418734 00130598 00000104 00000072 TOTALCMD+0x13e8a
0013fd2c 7e418816 003e09de 00130598 00000104 user32!InternalCallWinProc+0x28
0013fd94 7e42a013 00000000 003e09de 00130598 user32!UserCallWinProcCheckWow+0x150
0013fdc4 7e42a039 ffff04d9 00130598 00000104 user32!CallWindowProcAorW+0x98
0013fde4 004432f1 ffff04d9 00130598 00000104 user32!CallWindowProcW+0x1b
0013fe0c 00413e8a 00000104 00000072 203d0001 TOTALCMD+0x432f1
0013fe24 7e418734 00130598 00000104 00000072 TOTALCMD+0x13e8a
0013fe50 7e418816 003e09cd 00130598 00000104 user32!InternalCallWinProc+0x28
0013feb8 7e4189cd 00000000 003e09cd 00130598 user32!UserCallWinProcCheckWow+0x150
0013ff18 7e418a10 0013ff4c 00000000 0013ff6c user32!DispatchMessageWorker+0x306
0013ff28 004194ce 0013ff4c 0013ff7c 004194e9 user32!DispatchMessageW+0xf
0013ff6c 00419566 7ffd4000 00419720 0013ff94 TOTALCMD+0x194ce
0013ff8c 0069c6e7 0013ffb4 0069c702 0013ffc0 TOTALCMD+0x19566
0013ffc0 7c817077 00370034 00310031 7ffd4000 TOTALCMD+0x29c6e7
0013fff0 00000000 0069c340 00000000 00000000 kernel32!BaseProcessStart+0x23


FOLLOWUP_IP: 
SciLister+194ff
018094ff ??               ???

SYMBOL_STACK_INDEX:  8

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  SciLister+194ff

MODULE_NAME:  SciLister

IMAGE_NAME:  SciLister.wlx

DEBUG_FLR_IMAGE_TIMESTAMP:  43551cc5

STACK_COMMAND:  .ecxr ; kb

FAILURE_BUCKET_ID:  ACCESS_VIOLATION_SciLister+194ff

BUCKET_ID:  ACCESS_VIOLATION_SciLister+194ff

Followup: MachineOwner
---------
Author of Total Commander
https://www.ghisler.com
Top
prantlf
Junior Member
Junior Member
Posts: 3
Joined: 2009-08-19, 09:07 UTC

Post by *prantlf »

Hmm, you're right. I'm sorry, I should've looked to the dump first.

I renamed the directory plugins in the TC installation directory. Unfortunately SciLister was in another directory, drat.

Anyway, it helped. Recently I upgraded SciTE to the version 2.0. It seems that the latest SciLister 0.1.1 is not compatible with the latest Scintilla. I'm going to inform the author.

Thank you for the help!
Ferda
Top
prantlf
Junior Member
Junior Member
Posts: 3
Joined: 2009-08-19, 09:07 UTC

Post by *prantlf »

I wrote the author of the plugin Adam Strzelecki about it. The last version of Scintilla&SciTE which works with TC SciLister is 1.74.

Thanks for the help,
Ferda
Top
Post Reply

Return to “TC Behaviour which will not be changed”