[Bug 49437] Segmentation fault (core dumped) even on winecfg or wineconsole on FreeBSD

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=49437

--- Comment #8 from Damjan Jovanovic <damjan.jov at gmail.com> ---
(In reply to Sean C. Farley from comment #5)
> Created attachment 67808 [details]
> ktrace of winecfg execution
> 
> I am running 12.1-STABLE r363031 amd64 (r363017 was the last commit within
> the tree I am running).  This has the patch you submitted to FreeBSD for
> #49139.
> 
> Wine was built from ports in an i386 jail using an edited
> emulators/i386-wine-devel port to build later versions than currently in
> ports for it.  It only uses two patches from the emulators/wine-devel port
> located here: 
> https://svnweb.freebsd.org/ports/head/emulators/wine-devel/files/  The only
> patch that affects the run of Wine would be patch-dlls_kernel32_Makefile.in.
> 
> This is the only difference between my running system and changes to
> anything within libexec/rtld-elf: 
> https://svnweb.freebsd.org/base/stable/12/libexec/rtld-elf/rtld.
> c?r1=363372&r2=363371&pathrev=363372
> 
> I am attaching the failure at the end of a ktrace when attempting to run
> winecfg.  There is an "mmap -1 errno 22 Invalid argument" right before
> opening ntdll.dll.so.  Interestingly, the first ktrace showed
> code=SEGV_MAPERR while all other runs (at least 20) showed code=SEGV_ACCERR.
> 

This might be something:

 56486 wine     CALL 
mmap(0,0x1000,0<PROT_NONE>,0x1012<MAP_PRIVATE|MAP_FIXED|MAP_ANON>,0xffffffff,0,0)
 56486 wine     RET   mmap -1 errno 22 Invalid argument

I can't find such a line in my own ktrace, and MAP_FIXED shouldn't really be
getting used much on FreeBSD without MAP_EXCL.

> Just checking, are you testing amd64, i386 or i386 on amd64?  I had just
> noticed that Adrien, who opened this issue, had labeled the hardware as
> x86-64 (amd64), so something may be amiss with my setup compared to his.

i386 on amd64

-- 
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.