gmane.os.inferno.general

Segmentation violation

Hi!

I'm trying to run Inferno on Linux. The installation runs smoothly and executing
% /usr/inferno/Linux/386/bin/emu
runs ok too, ending up with the inferno shell, but when I execute
; wm/wm
the window manager shows for 0.5 seconds and then it dies with:
Locking assertion failure. Backtrace:
#0 /usr/lib/libxcb-xlib.so.0 [0xb7d1c727]
#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x2e) [0xb7d1c7de]
#2 /usr/lib/libX11.so.6 [0xb7e996c8]
#3 /usr/lib/libX11.so.6 [0xb7e99e42]
#4 /usr/lib/libX11.so.6 [0xb7e9a15f]
#5 /usr/lib/libX11.so.6(XNextEvent+0x8b) [0xb7e81c7b]
#6 /usr/inferno/Linux/386/bin/emu [0x804c644]
#7 /usr/inferno/Linux/386/bin/emu [0x804afe9]
#8 /lib/libc.so.6(clone+0x5e) [0xb7dde20e]
emu: xcb_xlib.c:73: xcb_xlib_lock: Assertion `!c->xlib.lock' failed.
EMU: faults: Segmentation violation

Any feedback is welcome.

Markus

headers

hugo rivera | 17 Mar 19:29

Re: Segmentation violation

I think I had the same problem while trying to run the wm/wm or any
graphical app on OpenSuse 10.3/amd64.
Finally I had to move to debian. Which distro are you using?

Hugo

2008/3/17, aon.912189943.2@... <aon.912189943.2@...>:
> Hi!
>
> I'm trying to run Inferno on Linux. The installation runs smoothly and
> executing
> % /usr/inferno/Linux/386/bin/emu
> runs ok too, ending up with the inferno shell, but when I execute
> ; wm/wm
> the window manager shows for 0.5 seconds and then it dies with:
> Locking assertion failure.  Backtrace:
> #0 /usr/lib/libxcb-xlib.so.0 [0xb7d1c727]
> #1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x2e) [0xb7d1c7de]
> #2 /usr/lib/libX11.so.6 [0xb7e996c8]
> #3 /usr/lib/libX11.so.6 [0xb7e99e42]
> #4 /usr/lib/libX11.so.6 [0xb7e9a15f]
> #5 /usr/lib/libX11.so.6(XNextEvent+0x8b) [0xb7e81c7b]
> #6 /usr/inferno/Linux/386/bin/emu [0x804c644]
> #7 /usr/inferno/Linux/386/bin/emu [0x804afe9]
> #8 /lib/libc.so.6(clone+0x5e) [0xb7dde20e]
> emu: xcb_xlib.c:73: xcb_xlib_lock: Assertion `!c->xlib.lock' failed.
> EMU: faults: Segmentation violation
>
> Any feedback is welcome.
>
> Markus
>
>

headers

aon.912189943.2 | 17 Mar 20:09

Re: Segmentation violation

----- Ursprüngliche Nachricht -----
Von: "hugo rivera"
Erhalten: 17.03.2008 19:29
An: "hugo rivera" , inferno-list-VZPH4yCFGSyB+jHODAdFcQ@public.gmane.org
@public.gmane.org> <at> gmail.com>

> I think I had the same problem while trying to run the wm/wm or any
> graphical app on OpenSuse 10.3/amd64.
> Finally I had to move to debian. Which distro are you using?

CRUX Linux. Isn't it more or less a X error?

headers

Ostap Cherkashin | 17 Mar 23:20

Re: Segmentation violation

The same on my laptop (Ubuntu Hardy, X.Org X Server 1.4.0.90). It
appears to be very similar to the problem with Java displaying GUI
(http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6532373).

Try using the following:
$ export LIBXCB_ALLOW_SLOPPY_LOCK=1

It works for me for both wm/wm and Java.

HTH

On Mon, Mar 17, 2008 at 8:10 PM,  <aon.912189943.2@...> wrote:
>
>
> ----- Ursprüngliche Nachricht -----
> Von: "hugo rivera"
> Erhalten: 17.03.2008 19:29
> An: "hugo rivera" , inferno-list@...
>
>
>
>
>
>
> > I think I had the same problem while trying to run the wm/wm or any
> > graphical app on OpenSuse 10.3/amd64.
> > Finally I had to move to debian. Which distro are you using?
>
> CRUX Linux. Isn't it more or less a X error?
>
>
>
>
>
>
>

headers

Charles Forsyth | 18 Mar 03:19

Re: Segmentation violation

from the libxcb patch notes

   This is a workaround for X11 applications which have locking bugs
  that will trigger assertions when libxcb is used. An environment variable,
  LIBXCB_ALLOW_SLOPPY_LOCK, can be set to skip the check that the display lock
  has been set correctly. This will not be merged upstream as the XCB
  developers have decided to be strict in exposing the bugs so they are fixed
  in the appropriate location.

could they be any more vague?  is there a sensible note somewhere that
defines "locking bugs" "set correctly" "appropriate location"?
i couldn't find it on a quick google.
i did find that quite a few applications seem to need it.
i suppose i am happy if Inferno is not one of them, so it would
be useful to know what the problem actually is.

headers

David Leimbach | 17 Mar 23:25

Re: Segmentation violation

On Mon, Mar 17, 2008 at 10:39 AM, <aon.912189943.2-Tswl7xcH0yE@public.gmane.org> wrote:

Hi!

I'm trying to run Inferno on Linux. The installation runs smoothly and executing
% /usr/inferno/Linux/386/bin/emu
runs ok too, ending up with the inferno shell, but when I execute
; wm/wm
the window manager shows for 0.5 seconds and then it dies with:
Locking assertion failure. Backtrace:
#0 /usr/lib/libxcb-xlib.so.0 [0xb7d1c727]
#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x2e) [0xb7d1c7de]
#2 /usr/lib/libX11.so.6 [0xb7e996c8]
#3 /usr/lib/libX11.so.6 [0xb7e99e42]
#4 /usr/lib/libX11.so.6 [0xb7e9a15f]
#5 /usr/lib/libX11.so.6(XNextEvent+0x8b) [0xb7e81c7b]
#6 /usr/inferno/Linux/386/bin/emu [0x804c644]
#7 /usr/inferno/Linux/386/bin/emu [0x804afe9]
#8 /lib/libc.so.6(clone+0x5e) [0xb7dde20e]
emu: xcb_xlib.c:73: xcb_xlib_lock: Assertion `!c->xlib.lock' failed.
EMU: faults: Segmentation violation

Any feedback is welcome.

This is why I don't use X11 :-)

You did say ANY feedback...

There is a framebuffer Inferno out there for linux "somewhere" also, in case you continue having trouble.

Markus

headers

aon.912189943.2 | 18 Mar 09:06

Re: Segmentation violation

> Try using the following:
> $ export LIBXCB_ALLOW_SLOPPY_LOCK=1

Thanks, now it works.