x11-toolkits/xview (actually contool)

[Carlos A. M. dos Santos]

2009/8/6 Mel Flynn <mel.flynn+fbsd.ports at mailing.thruhere.net>:
> On Wednesday 05 August 2009 20:08:55 Doug Barton wrote:
>> Ok, so now I'm up to the point where starting contool give me this:
>>
>> contool
>> Assertion failed: (ret != inval_id), function _XAllocID, file
>> xcb_io.c, line 378.
>> Abort trap: 6 (core dumped)
>
> You get a better a log if you install contool unstripped [1]:
> (gdb) bt
> #0  0x28463eb7 in kill () from /lib/libc.so.7
> #1  0x28463e16 in raise () from /lib/libc.so.7
> #2  0x28462a1a in abort () from /lib/libc.so.7
> #3  0x28448ee6 in __assert () from /lib/libc.so.7
> #4  0x28284d46 in _XAllocID (dpy=0x28524600) at xcb_io.c:378
> #5  0x2818e11c in server_init (parent=0, server_public=676345056, avlist=0xbfbfd944)
>    at server.c:746
> #6  0x281f33b9 in xv_create_avlist (parent=0, pkg=0x0, avlist=0xbfbfd944) at xv.c:391
> #7  0x281f315b in xv_create (parent=0, pkg=0x28210040) at xv.c:307
> #8  0x281f520a in xv_init (attr1=1241974786) at xv_init.c:308
> #9  0x0804b801 in main (argc=1, argv=0xbfbfe6e4) at contool.c:777
>
> Which points to xv_init from xview as the culprit. Since that is
---8<---

Nope. It points to XAllocID as the culprit, so far, which in its turn
points to _XAllocID, in xcb_io.c, from libX11. Try building libX11
without XCB (see PR 137373). I'd test it myself but I'm running AMD64
here and Xview is maked as broken on this architecture.

-- 
My preferred quotation of Robert Louis Stevenson is "You cannot
make an omelette without breaking eggs". Not because I like the
omelettes, but because I like the sound of eggs being broken.