Sync bug on Mousewheel scroll down

[Samuel]

I thought of updating my mouse driver but I didn't wanted to "destroy" the ability to reproduce the bug.

[Samuel]

I updated mouse driver and I still get it.

Code: Select all

Application Error
---------------------------
Exception EAccessViolation in module TOTALCMD.EXE at 63295A17.
Access violation at address 63696C43. Read of address 63696C43.

Mh are you shure the debug version is implemented in the standalone lister tool? Theres no stack in the error message.

I wonder why I am the only one. Also this empty titlebar bug occurs from time to time. But never could reproduce the two bugs for 100%.

[ghisler(Author)]

Mh are you shure the debug version is implemented in the standalone lister tool?

You are right, it isn't! I will add it.

[Samuel]

Perhaps you fixed it wrong?
Now I got 2 of these errors.

Code: Select all

---------------------------
Application Error
---------------------------
Exception EAccessViolation in module TOTALCMD.EXE at 00000000.
Access violation at address 00000000. Read of address 00000000.
---------------------------
OK   
---------------------------

I really really am exited what this bug is about.

[ghisler(Author)]

Address 0 means that Total Commander (or some driver/dll) tried to call a function which doesn't exist, or wasn't loaded.

[Samuel]

Don't you always check for 0 pointer?
Or is this the check? Then you should additionally return an custom errorstring or errornumber for each check. So you could get the linenumber from the error.

[ghisler(Author)]

No, it's not the check. I do check for 0 pointers, but this error seems to be outside my code because there is no stack trace - beta 6 now supports stack traces also in the sync tool.

[Samuel]

I know. (read it in history)
This is exactly the beta I used for the above error:
http://www.ghisler.ch/board/viewtopic.php?p=176846#176846

Edit: So I asked if you fixed it wrong...
Anything I can do?

[ghisler(Author)]

No, I tried it - standalone sync should give you the stack trace now when the error happens in my functions (or code called by my functions). I assume that the error occurs somewhere in the mouse driver even before it reaches my code...

[Samuel]

Fixed in TC 7.5 pb8. - Thanks a lot.

[ghisler(Author)]

Great, thanks!