fixme:mountmgr:harddisk_ioctl and err:seh:setup_exception

[leshyk]

It seems, that exception fixme:mountmgr:harddisk_ioctl often comes together with 'err:seh:setup_exception'.

The program had been working fine until I have added the registration key to the registry, after that the following errors happen:

Code: Select all

fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d004 (device=4 access=3 func=401 method=0)
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d004 (device=4 access=3 func=401 method=0)
err:seh:setup_exception_record stack overflow 1924 bytes in thread 0024 eip 7bc3e41f esp 00230bac stack 0x230000-0x231000-0x330000

Before entering of the key only one error of the first type appeared without any problems:

Code: Select all

fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d004 (device=4 access=3 func=401 method=0)

What do the errors means and what should be avoided in the application to eliminate this error?
Note that in the application no additional functionality appears.

Thank you.

[dimesio]

If the app is working, don't worry about terminal messages.

[leshyk]

I'm sorry for uncertainty.

The program had stopped working after edit the key in registry (program registration procedure), it is a problem. The output with that error was shown on the first box...

[dimesio]

What app is this? Is editing the registry the way the key is supposed to be entered for this app? (Most apps have a GUI dialog to enter registration keys.)

How did you edit the registry? You should have used regedit; if you tried to edit the file directly in a text editor, that could be the cause of the problem.

Also, what version of Wine are you using? If it's not the latest development release, upgrade.

[leshyk]

This is a windows not-unicode application. It is an util useful in science of Graph Mining.

The registry is edited with

Code: Select all

wine regedit key.reg

And yes, it is a supposed way to edit the registry.

After upgrade:

Code: Select all

wine --version

wine-1.5.19

And after upgrade the errors changed. If I clear the registry and run the application I have the following output:

Code: Select all

p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d004 (device=4 access=3 func=401 method=0)

... and, of course, the application says that the trial is finished.

After applying the registry key, I have the following output:

Code: Select all

p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d004 (device=4 access=3 func=401 method=0)
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d004 (device=4 access=3 func=401 method=0)
err:heap:validate_block_pointer Heap 0xffbf0000: bad flags 00000003 for in-use arena 0xffbf2be8

... and application still says that the trial version is finished, so it is seems that there is a problem to read the registry key.

[leshyk]

After the new update

Code: Select all

$wine --version
wine-1.5.23

The behavior is the same as it is for the first message

Code: Select all

p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d004 (device=4 access=3 func=401 method=0)
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d004 (device=4 access=3 func=401 method=0)
err:seh:setup_exception_record stack overflow 1712 bytes in thread 0009 eip 7bc408c8 esp 00230c80 stack 0x230000-0x231000-0x330000

If I would like to find an error by myself what should I do? (i.e. instructions to take wine code and compile it).

[leshyk]

I am trying to find an error in the log

Code: Select all

WINEDEBUG=+all wine programm.exe 2> log.txt

In that log I have lines like:
...
18005.948:0009:Ret advapi32.RegQu000d: close_handle() = 0
...

which really means that there are two threads fighting for the log. How to switch off the logging of one thread, or how to preserve the valid log? Thank you