[Bug 36886] ST visual develop 4.3.0: crash when new workplace and project name is entered and OK is pressed

wine-bugs at winehq.org wine-bugs at winehq.org
Mon Jul 14 03:50:10 CDT 2014


http://bugs.winehq.org/show_bug.cgi?id=36886

vishal <mebro.power at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from vishal <mebro.power at gmail.com> ---
(In reply to vishal from comment #0)
> Created attachment 48979 [details]
> terminal log file
> 
> File can be download from following direct web link.
> http://www.st.com/web/catalog/tools/FM147/CL1794/SC1808/SS1767/PF210567#
> 
> sha1sum /home/vishal/sttoolset.exe
> 0da848d6cedf137fb48fe63bba21470c6f971883  /home/vishal/sttoolset.exe
> 
> When we select 
> File->New workspace->create workspace and project->{entering workspace
> name]->[entering project name]->[select toolchain 'st assembler link']->OK
> 
> program crashes...the same behaviour is repeated with all the toolchain in
> the list(project menu)


Hello (In reply to Anastasius Focht from comment #1)
> Hello vishal,
> 
> --- snip ---
> err:ole:CoGetClassObject no class object
> {00000100-0000-0010-8000-00aa006d2ea4} could be created for context 0x1
> wine: Unhandled page fault on read access to 0x00000000 at address 0x893dca
> (thread 0009), starting debugger...
> --- snip ---
> 
> You have a tainted/broken WINEPREFIX.
> 
> The app installs MS DAO on its own (no need for 'winetricks -q jet40').
> 
> Reinstall the app in clean (new!) 32-bit prefix.
> 
> Works fine for me here in clean 32-bit WINEPREFIX:
> 
> --- snip ---
> $ pwd
> /home/focht/.wine/drive_c/Program Files/STMicroelectronics/st_toolset/stvd
> 
> $ WINEDEBUG=+tid,+seh,+relay wine ./stvdebug.exe >>log.txt 2>&1
> ...
> 0023:Call KERNEL32.GetProcAddress(7e2e0000,782adc4c "CoGetClassObject")
> ret=7829744e
> 0023:Ret  KERNEL32.GetProcAddress() retval=7e2e3a18 ret=7829744e
> 0023:Call
> ole32.CoGetClassObject(781d2854,00000001,00000000,781d2000,0033b288)
> ret=78247365
> 0023:Call
> KERNEL32.FindActCtxSectionGuid(00000001,00000000,00000004,781d2854,0033b11c)
> ret=7e2fa628
> 0023:Ret  KERNEL32.FindActCtxSectionGuid() retval=00000000 ret=7e2fa628
> 0023:Call ntdll.RtlInitUnicodeString(0033b030,0033b082
> L"CLSID\\{00000100-0000-0010-8000-00AA006D2EA4}") ret=7e2f462d
> 0023:Ret  ntdll.RtlInitUnicodeString() retval=0033b030 ret=7e2f462d
> 0023:Call ntdll.NtOpenKey(0033b07c,00020019,0033b038) ret=7e2f4649
> 0023:Ret  ntdll.NtOpenKey() retval=00000000 ret=7e2f4649
> 0023:Call ntdll.RtlNtStatusToDosError(00000000) ret=7e2f4654
> 0023:Ret  ntdll.RtlNtStatusToDosError() retval=00000000 ret=7e2f4654
> 0023:Call ntdll.RtlInitUnicodeString(0033b030,7e3d7e1c L"InprocServer32")
> ret=7e2f462d
> 0023:Ret  ntdll.RtlInitUnicodeString() retval=0033b030 ret=7e2f462d
> 0023:Call ntdll.NtOpenKey(0033b160,00020019,0033b038) ret=7e2f4649
> 0023:Ret  ntdll.NtOpenKey() retval=00000000 ret=7e2f4649
> 0023:Call ntdll.RtlNtStatusToDosError(00000000) ret=7e2f4654
> 0023:Ret  ntdll.RtlNtStatusToDosError() retval=00000000 ret=7e2f4654
> 0023:Call advapi32.RegCloseKey(0000010c) ret=7e2f90c2
> 0023:Ret  advapi32.RegCloseKey() retval=00000000 ret=7e2f90c2
> 0023:Call advapi32.RegQueryValueExW(00000110,7e3d7dac
> L"ThreadingModel",00000000,0033ae60,0033ae68,0033ae64) ret=7e2fa0d0
> 0023:Ret  advapi32.RegQueryValueExW() retval=00000000 ret=7e2fa0d0
> 0023:Call
> advapi32.RegQueryValueExW(00000110,00000000,00000000,0033ae6c,0033ac5c,
> 0033ae68) ret=7e2f6e92
> 0023:Ret  advapi32.RegQueryValueExW() retval=00000000 ret=7e2f6e92
> 0023:Call ntdll.RtlAllocateHeap(00110000,00000000,00000014) ret=7e2f6c47
> 0023:Ret  ntdll.RtlAllocateHeap() retval=001bc340 ret=7e2f6c47
> 0023:Call KERNEL32.LoadLibraryExW(0033aebe L"C:\\Program Files\\Common
> Files\\Microsoft Shared\\DAO\\Dao360.dll",00000000,00000008) ret=7e2f47c1
> ...
> 0023:Ret  PE DLL (proc=0x1b73f33f,module=0x1b730000
> L"Dao360.dll",reason=PROCESS_ATTACH,res=(nil)) retval=1
> 0023:Ret  KERNEL32.LoadLibraryExW() retval=1b730000 ret=7e2f47c1
> ...
> 0023:Ret  ole32.CoGetClassObject() retval=00000000 ret=78247365
> ...
> --- snip ---
> 
> $ sha1sum sttoolset.zip 
> 5bfb02df5e7ca7ec4c8946a73b77c6c1175bd0eb  sttoolset.zip
> 
> $ nexus4[~/Downloads] du -sh sttoolset.zip 
> 81M	sttoolset.zip
> 
> $ nexus4[~/Downloads] wine --version
> wine-1.7.22
> 
> Regards




Hello Anastasius Focht,
first thank for quick and pointed reply.
Now the problem is resolved. 

Second issue, when i try to open workspace it gives message "fail to load
workspace possible file corrupt"..so i have to used new workspace and in that
creat workspace from project..then it work..though i can adjust...but is their
any way where it can be resolved....


finally, if you don't mind, their is one more issue with the same program (st
visual develop)...as it is IDE for microcontroller, so when i try to connect to
the development board via USB..connection error (usb://usb) occurs...
After searching on google i come to know that wine can not support usb...i am
using wine 1.7.21

So, is their any other way of connecting to usb development board. Linux used
to detect my device(stlink). Since in virtualbox i can enable my st-link.

thanks...
vishal

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.


More information about the wine-bugs mailing list