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.
http://bugs.winehq.org/show_bug.cgi?id=1947
------- Additional Comments From marcus(a)jet.franken.de 2004-19-01 15:53 -------
it is probably not related to TEMP or TMP env var.
Can you run with -debugmsg +relay, and quote the 200 lines before
the "Unable ... " line? (Or attach the whole log compressed)
--
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 eetasoft(a)online.ee 2004-19-01 14:10 -------
Created an attachment (id=497)
--> (http://bugs.winehq.org/attachment.cgi?id=497&action=view)
wine -debugmsg +dosfs log
Here is output from wine -debugmsg +dosfs ....
using /usr/bin/ps2pdf testprint.ps testprint.pdf in
/home/andrus directory.
As I wrote, gs prints an error
**** Unable to open the initial device, quitting.
to wine console. This error is visible in the attached log file.
--
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 marcus(a)jet.franken.de 2004-19-01 01:00 -------
axctually this should work, there is code handling TEMP and TMP
in files/directory.c.
can you run with -debugmsg +dosfs ? Do you get errors on the textconsole?
--
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=1946
zippy(a)cs.brandeis.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #496|WINE (not winex): |WINE (not winex):
description|wine/libs/wpp/wpp.y - this |wine/libs/wpp/ppy.y - this
|is the file that bison |is the file that bison
|chokes on |chokes on
--
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=1946
zippy(a)cs.brandeis.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #496|WINE (not winex): this is |WINE (not winex):
description|the file that bison chokes |wine/libs/wpp/wpp.y - this
|on |is the file that bison
| |chokes on
--
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=1894
------- Additional Comments From mike(a)theoretic.com 2004-18-01 17:05 -------
I should note here that the fix (using ld scripts) is known, just nobody
implemented it yet.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.winehq.org/show_bug.cgi?id=1947
Summary: Illegal contents of environment variable TEMP passed to
Linux application
Product: Wine
Version: 20031212
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-binary
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: eetasoft(a)online.ee
If Windows application runs Linux program, WINE passes a Windows
path to Linux application through TEMP environment variable.
This causes some applications, like Ghostscript, to fail.
To reproduce:
1. Create a file test.ps in home directory.
2. From an application running under WINE, invoke Linux command
/usr/bin/ps2pdf test.ps test.pdf
If you are using Visual FoxPro, this can be done using command
RUN /N /usr/bin/ps2pdf test.ps test.pdf
3. Observed result:
test.pdf file is not created
Cryptic message
**** unable to open the initial device, quitting
appears in WINE console
Note. Yes, this can be fixed using unset TEMP command.
However, I expect that WINE will not pass TEMP variable in a such way.
--
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=1946
------- Additional Comments From zippy(a)cs.brandeis.edu 2004-18-01 14:58 -------
Downgrading to Bison 1.35 (bison-1.35-3mdk.i586.rpm) is a workaround. Wine
compiles without error using this version of Bison.
--
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-18-01 14:39 -------
it should not do this,
either glibc, xfree86 or wine is not using threadsafe constructs.
--
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=1946
zippy(a)cs.brandeis.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #494|tools/mcy.y - file that |WINEX tools/mcy.y (please
description|results in error |ignore. WINE attachment
| |below)
--
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=1946
zippy(a)cs.brandeis.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #493|auto-generated config.h file|WINEX auto-generated
description| |config.h file, please ignore
| |(WINE config as sep attach)
--
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=1946
zippy(a)cs.brandeis.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
------- Additional Comments From zippy(a)cs.brandeis.edu 2004-18-01 14:00 -------
Marcus pointed out that this error was for WineX. My mistake.
I downloaded Wine and got the same error. Here is the error for Wine (not Winex):
make[2]: Leaving directory `/home/patrick/wine/wine/libs/wine'
make[2]: Entering directory `/home/patrick/wine/wine/libs/wpp'
bison -y -ppp -d -t ./ppy.y
make[2]: *** [y.tab.c] Broken pipe
make[2]: Leaving directory `/home/patrick/wine/wine/libs/wpp'
make[1]: *** [wpp] Error 2
make[1]: Leaving directory `/home/patrick/wine/wine/libs'
make: *** [libs] Error 2
Compilation failed, aborting install.
[patrick@localhost wine]$
--
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.
marcus(a)jet.franken.de wrote:
> please report winex bugs to the winex guys, this is for WINEHQ wine bugs.
Marcus is right. I was using the Winex source. Sorry about this.
I'll download the regular Wine source and see if the same bug occurs.
--Pat
http://bugs.winehq.org/show_bug.cgi?id=1946
marcus(a)jet.franken.de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
------- Additional Comments From marcus(a)jet.franken.de 2004-18-01 13:37 -------
please report winex bugs to the winex guys, this is for WINEHQ wine bugs.
Probalby your bison version is too new, try a downgrade to an earlier one :/
--
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=1946
zippy(a)cs.brandeis.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|wine-misc |wine-tools
--
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.
Quoting Wine Bugs:
>
> http://bugs.winehq.org/show_bug.cgi?id=1944
>
>
>
>
>
> ------- Additional Comments From marcus(a)jet.franken.de 2004-17-01 19:20 -------
> how old is your system?
FreeBSD-4.9-STABLE -- system updated at least once a week
from the latest cvsup sources. So, you can count it as being
practically always the latest and greatest 4.9.
> what is your XFree86 version?
Otherwise 4.3.0, but the server is snap 4.3.99.15.
Cheers,
// jau
.--- ..- -.- -.- .- .- .-.-.- ..- -.- -.- --- -. . -.
/ Jukka A. Ukkonen, Mawit Ltd, Finland
/__ M.Sc. (sw-eng & cs) (Phone) +358-500-606-671
/ Internet: Jukka.Ukkonen(a)Mawit.Com (Home) +358-9-6215-280
/ Internet: ukkonen(a)nic.funet.fi
v Internet: jau(a)iki.fi
+ + + + My opinions are mine and mine alone, not my employers. + + + +
http://bugs.winehq.org/show_bug.cgi?id=1945
Summary: MYOB v11, strange dialog box on load, crashes after
short period of time
Product: Wine
Version: 20031212
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wine-binary
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: derek(a)dereksplace.co.nz
MYOB version 12 (from www.myob.co.nz) displays dialog box (sic) "FALT is needs
that bit cleared. [OK]" Click [OK], dialog appears 36 times before MYOB starts.
Seems to run okay for about 2-3 minutes before hanging.
Each time initial dialog is clicked, console log shows:
fixme:accel:CreateAcceleratorTableA should check that the accelerator
descriptions are valid, return NULL and SetLastError() if not.
When trying to open it's data file (standard Windows File Open dialog appears)
console log shows:
fixme:commdlg:GetFileName95 Flags 0x00002000 not yet implemented
err:dosfs:DRIVE_ReadSuperblock Couldn't open device '' for drive F: ! (not
available or symlink not valid ?)
err:dosfs:DRIVE_ReadSuperblock Can't read drive volume info ! Either pre-set it
or make sure the device to read it from is accessible !
err:dosfs:DRIVE_GetLabel Invalid or unreadable superblock on (F:).
fixme:dosfs:DRIVE_GetSerialNumber Serial number reading from file system on
drive F: not supported yet.
During program execution, this message appears numerous (40+) times, whenever
the mouse pointer hovers over a link or button in the MYOB gui:
fixme:font:SetMapperFlags (0x730, 0x00000000): stub - harmless
After a period of time (2-3 minutes) or after opening a few child windows, MYOB
hangs. Console shows:
fixme:msvcrt:_XcptFilter (-1073741819,0x406cf63c)semi-stub
wine: Unhandled exception (thread 001f), starting debugger...
WineDbg starting on pid 1e
Loaded debug information from ELF 'wine' ((nil))
No debug information in 32bit DLL 'C:\myob12\Myob.exe' (0x400000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\NTDLL.DLL' (0x40200000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\KERNEL32.DLL' (0x40490000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\ADVAPI32.DLL' (0x40a50000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\GDI32.DLL' (0x408a0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\USER32.DLL' (0x40720000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\IPHLPAPI.DLL' (0x40aa0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WS2_32.DLL' (0x40ac0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\NETAPI32.DLL' (0x40a80000)
No debug information in 32bit DLL 'C:\MYOB12\CTMYOB32.DLL' (0x10000000)
No debug information in 32bit DLL 'C:\MYOB12\MYOBSP32.DLL' (0x406d0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\RPCRT4.DLL' (0x40c40000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\OLE32.DLL' (0x40bc0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SHLWAPI.DLL' (0x40c90000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\COMCTL32.DLL' (0x40ce0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SHELL32.DLL' (0x40b30000)
No debug information in 32bit DLL 'C:\MYOB12\CPDF.DLL' (0x40add000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\LZ32.DLL' (0x40d90000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSVCRT.DLL' (0x40dc0000)
No debug information in 32bit DLL 'C:\MYOB12\XERCES.DLL' (0x12000000)
No debug information in 32bit DLL 'C:\MYOB12\MFC42.DLL' (0x73dd0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WINSPOOL.DRV' (0x40e80000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\COMDLG32.DLL' (0x40e00000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\X11DRV.DLL' (0x40f60000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\VERSION.DLL' (0x43290000)
No debug information in 32bit DLL 'C:\MYOB12\CFX2032.DLL' (0x4322d000)
Unhandled exception: page fault on read access to 0x40430000 in 32-bit code
(0x4010574c).
In 32-bit mode.
0x4010574c (NTDLL.DLL.memcpy+0x1c): repe movsl (%esi),%es:(%edi)
Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>syntax
error
Wine-dbg>syntax error
Wine-dbg>syntax error
Wine-dbg>syntax error
The last line repeats for quite some time, sometimes the only way to get out of
it is to kill the terminal session. If Ctrl-C is pressed in the debugger (if it
stops prompting) then this message appears:
err:seh:setup_exception nested exception on signal stack in thread 001f eip
400466c6 esp 40016bac stack 0x405d0000-0x406d0000
But more often than not even if debugger is stopped and control is returned to
the bash prompt the last line starts scrolling all over the screen (no line feed
beterrn messages) and the terminal must then be killed.
Application Details:
MYOB version 12 (New Zealand Customised version) from http://www.myob.co.nz)
Running on Mandrake 9.2 Linux 2.4.22-10mdk
Wine 20031212
--
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-17-01 19:20 -------
how old is your system?
what is your XFree86 version?
--
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.