Bug 267732 - emulators/wine: 'Thread 0x6224c000 has called pthread_exit() from a destructor. POSIX 1003.1 1996 s16.2.5.2 does not allow this!'
Summary: emulators/wine: 'Thread 0x6224c000 has called pthread_exit() from a destructo...
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-12 21:06 UTC by Martin Filla
Modified: 2023-08-27 20:46 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Filla 2022-11-12 21:06:45 UTC
Hi,
I tried running half-life on my machine and I have a problem with Fatal error 'Thread 0x6224c000 has called pthread_exit() from a destructor. POSIX 1003.1 1996 s16.2.5.2 does not allow this

010c:err:d3d:wined3d_debug_callback 0x58fe38: "GL_INVALID_FRAMEBUFFER_OPERATION error generated. Framebuffer bindings are not framebuffer complete.".
00f4:fixme:win:LockWindowUpdate (00050040), partial stub!
00f4:fixme:win:LockWindowUpdate (00000000), partial stub!
00f4:fixme:win:LockWindowUpdate (00050040), partial stub!
00f4:fixme:win:LockWindowUpdate (00000000), partial stub!
00f4:fixme:win:LockWindowUpdate (00050040), partial stub!
00f4:fixme:win:LockWindowUpdate (00000000), partial stub!
00f4:fixme:win:LockWindowUpdate (00050040), partial stub!
00f4:fixme:win:LockWindowUpdate (00000000), partial stub!
00f4:fixme:win:LockWindowUpdate (00050040), partial stub!
00f4:fixme:win:LockWindowUpdate (00000000), partial stub!
010c:err:d3d:wined3d_debug_callback 0x58fe38: "GL_OUT_OF_MEMORY error generated. Failed to allocate memory for buffer object.".
00f4:err:system:ChangeDisplaySettingsExW Changing L"\\\\.\\DISPLAY1" display settings returned -2.
wine: Unhandled page fault on write access to 00000004 at address 66A3D48B (thread 00f4), starting debugger...
wineserver: file_set_error() can't map error: Cannot allocate memory
wine client error:f4: write: Bad file descriptor
Fatal error 'Thread 0x6224c000 has called pthread_exit() from a destructor. POSIX 1003.1 1996 s16.2.5.2 does not allow this!' at line 221 in file /usr/src/lib/libthr/thread/thr_exit.c (errno = 9)
wine client error:f4: write: Bad file descriptor
Fatal error 'Thread 0x6224c000 has called pthread_exit() from a destructor. POSIX 1003.1 1996 s16.2.5.2 does not allow this!' at line 221 in file /usr/src/lib/libthr/thread/thr_exit.c (errno = 9)
wine client error:f4: write: Bad file descriptor
Fatal error 'Thread 0x6224c000 has called pthread_exit() from a destructor. POSIX 1003.1 1996 s16.2.5.2 does not allow this!' at line 221 in file /usr/src/lib/libthr/thread/thr_exit.c (errno = 9)
wine client error:f4: write: Bad file descriptor
Fatal error 'Thread 0x6224c000 has called pthread_exit() from a destructor. POSIX 1003.1 1996 s16.2.5.2 does not allow this!' at line 221 in file /usr/src/lib/libthr/thread/thr_exit.c (errno = 9)
wine client error:f4: write: Bad file descriptor
Fatal error 'Thread 0x6224c000 has called pthread_exit() from a destructor. POSIX 1003.1 1996 s16.2.5.2 does not allow this!' at line 221 in file /usr/src/lib/libthr/thread/thr_exit.c (errno = 9)
wine client error:f4: write: Bad file descriptor
Fatal error 'Thread 0x6224c000 has called pthread_exit() from a destructor. POSIX 1003.1 1996 s16.2.5.2 does not allow this!' at line 221 in file /usr/src/lib/libthr/thread/thr_exit.c (errno = 9)
wine client error:f4: write: Bad file descriptor
Comment 1 Gerald Pfeifer freebsd_committer 2022-11-13 09:11:23 UTC
I acknowledge this report, just have to note that specific issues like
this are unlikely to get addressed this route.

To give you an idea, the upstream bug tracker features 4034 reports on
D3D issues alone, of which 509 are still open:

https://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=STAGED&bug_status=REOPENED&bug_status=NEEDINFO&component=d3d&limit=0&list_id=778180&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&product=Wine&query_format=advanced
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2023-08-23 05:43:48 UTC
Canonicalize assignment.
Comment 3 Gerald Pfeifer freebsd_committer 2023-08-27 20:46:57 UTC
What I can offer regarding this specific bug is that I have updated
emulators/wine-devel to version 8.11 and plan on shortly updating
emulators/wine to version 8.0.2 (see PR 272710 which also has a patch).

Wine on FreeBSD sadly is understaffed as it comes to developers and I 
am helping out when I can (having tried to hand over everything two,
three years ago).

Closing as "Overcome by Events" for lack of a better option...