http://bugs.winehq.org/show_bug.cgi?id=1944
------- Additional Comments From marcus(a)jet.franken.de 2004-20-01 03:37 -------
reporter, can you also compile with debug info
and get some line numbers?
also the place of the bus error would be of itnerest.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=1074
------- Additional Comments From the_riddlr(a)hotmail.com 2004-20-01 02:48 -------
I have the same error report on this bug.. Any resolution yet?
-James
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=1947
------- Additional Comments From rklazes(a)xs4all.nl 2004-20-01 01:53 -------
Marcus, the problem is that Linux applications do not understand
DOS style contents of the TEMP variable.
This what is happening:
$ TEMP=C:\\TEMP ps2pdf -
**** Unable to open the initial device, quitting.
A solution within wine would be to unset all such variables before
launching the Unix executable. My guess is that it is unlikely to
be accepted, similar changes for DOS paths in the program arguments
where dropped in favour of the tool "winepath". The external
solution (script) is the way to go.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=1948
Summary: Unhandled exception: unimplemented function
rpcrt4.dll.RpcNetworkIsProtseqValidA called in 32-bit
code
Product: Wine
Version: 20031212
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: altaykirecci(a)yahoo.com
CC: altaykirecci(a)yahoo.com
fixme:seh:EXC_RtlRaiseException call to unimplemented function
rpcrt4.dll.RpcNetworkIsProtseqValidA
wine: Unhandled exception (thread 0017), starting debugger...
WineDbg starting on pid 16
Loaded debug information from ELF 'wine' ((nil))
No debug information in 32bit DLL 'C:\Program Files\Microsoft
Office\Office\OUTLOOK.EXE' (0x30000000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\NTDLL.DLL' (0x401c0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\KERNEL32.DLL' (0x40450000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSVCRT.DLL' (0x78000000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\ADVAPI32.DLL' (0x408d0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\GDI32.DLL' (0x40a50000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\USER32.DLL' (0x40920000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\RPCRT4.DLL' (0x40ad0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\OLE32.DLL' (0x40870000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\COMCTL32.DLL' (0x40b10000)
No debug information in 32bit DLL 'C:\PROGRAM FILES\MICROSOFT
OFFICE\OFFICE\MSO9.DLL' (0x308c0000)
No debug information in 32bit DLL 'C:\PROGRAM FILES\MICROSOFT
OFFICE\OFFICE\OUTLLIB.DLL' (0x3a420000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\X11DRV.DLL' (0x40e30000)
No debug information in 32bit DLL 'C:\PROGRAM FILES\MICROSOFT
OFFICE\OFFICE\1033\OUTLLIBR.DLL' (0x3a950000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SHLWAPI.DLL' (0x418a0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SHELL32.DLL' (0x41820000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MPR.DLL' (0x418e0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\LZ32.DLL' (0x41910000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\VERSION.DLL' (0x41900000)
No debug information in 32bit DLL
'C:\PROG~FBU\COMM~CP1\SYSTEM\MAPI\1033\95\GAPI32.DLL' (0x3ff30000)
No debug information in 32bit DLL 'C:\PROGRAM FILES\COMMON
FILES\SYSTEM\MAPI\1033\95\MSMAPI32.DLL' (0x62100000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSI.DLL' (0x3f000000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WINMM.DLL' (0x41d70000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSVFW32.DLL' (0x41d40000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WINEOSS.DRV' (0x41de0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSACM32.DLL' (0x41e20000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSACM.DRV' (0x41e10000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MIDIMAP.DRV' (0x40dc0000)
No debug information in 32bit DLL 'C:\PROGRAM FILES\COMMON
FILES\SYSTEM\MAPI\1033\95\EMSABP32.DLL' (0x626f0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\OLEAUT32.DLL' (0x41fd0000)
No debug information in 32bit DLL
'C:\PROG~FBU\COMM~CP1\SYSTEM\MAPI\1033\95\OUTEX.DLL' (0x62030000)
No debug information in 32bit DLL 'C:\PROGRAM FILES\COMMON
FILES\SYSTEM\MAPI\1033\95\EMSUI32.DLL' (0x625d0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\RICHED20.DLL' (0x48000000)
Unhandled exception: unimplemented function rpcrt4.dll.RpcNetworkIsProtseqValidA
called in 32-bit code (0x40ad4056).
In 32-bit mode.
0x40ad4056 (RPCRT4.DLL..text+0x3056 in RPCRT4.DLL): jmp 0x40ad4050
(RPCRT4.DLL..text+0x3050 in RPCRT4.DLL)
how can i fix this problem.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=1944
gerald(a)pfeifer.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
------- Additional Comments From gerald(a)pfeifer.com 2004-19-01 17:24 -------
I can confirm this issue. Unfortunately, FreeBSD 4.x really has have had this
kind of problems for several months now.
As far as I can tell, this is not due to FreeBSD bugs, but rather to the fact
that Wine makes certain (implicit) assumptions about the underlying threading
model which are satisfied by current glibcs but not FreeBSD's libc.
What I strongly recommend in FreeBSD-land is to use a current version of GCC
(from the 3.2 or 3.3 series) to address some linking issues you may encounter
with libc_r. And you may want to give FreeBSD 5.x a try, whose threading model
is more similiar to the glibc one, I believe.
I'll try to get access to a FreeBSD 5.2-CURRENT system and see how Forte Agent,
which currently won't work on FreeBSD 4.9-STABLE with the failure mode described
in this bug, behaves.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=1945
marcus(a)jet.franken.de changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|gerald(a)pfeifer.com |
------- Additional Comments From marcus(a)jet.franken.de 2004-19-01 16:48 -------
argh. the last comment does not belong here. please ignore.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=1944
------- Additional Comments From marcus(a)jet.franken.de 2004-19-01 16:46 -------
from reporter:
Maybe it relies too much on glibc style threadsafe model.
In FreeBSD it is definitely not using glibc. The libraries
loaded by default are...
(mjolnir) 10:42 ~> ldd `which wine`
/usr/local/bin/wine:
libwine.so.1 => /usr/local/lib/libwine.so.1 (0x20130000)
libc.so.4 => /usr/lib/libc.so.4 (0x20148000)
libm.so.2 => /usr/lib/libm.so.2 (0x201e1000)
Actually I suppose the libc.so should be libc_r.so for FreeBSD
environments.
I am not quite convinced that libc.so really guarantees that
everything is really thread safe by any standards. Full POSIX
threadsafe model is supported by libc_r.so, which becomes
automatically linked in when the -pthread option is give to
cc/gcc. Obviously the objects should also be compiled using
the -D_THREAD_SAFE option.
If this is the explanation to the odd behaviour, this looks
like the automatic configure makes some false assumptions for
FreeBSD.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.