Comment 23 for bug 615690

Revision history for this message
In , rusivi2 (rusivi2-deactivatedaccount) wrote :

Created an attachment (id=30229)
WINEDEBUG=+relay,+tid,+seh,+msi wine AdbeRdr90_en_US.exe >>log.txt 2&>1

Performed a trace install through all dialogue boxes clicked via:

WINEDEBUG=+relay,+tid,+seh,+msi wine AdbeRdr90_en_US.exe >>log.txt 2&>1

I found where DefragmentFiles was called as close to the backtrace as possible, took a few thousand lines prior (starting at line 35264316), as well as a few hundred after the stack dump (ending at line 35271000) and attached it. The original file is 36830321 lines long, 2.8GB in size.

I did notice instances of DefragmentFiles as early as line 7896575 which suggests that it is checking for defragmentation throughout the install process. Makes a lot of sense to do so. However, I haven't figured out how towards the end of the install the DefragmentFiles custom action is causing the divide by zero error.