Re: x11-toolkits/xview (actually contool)
2009/8/6 Mel Flynn : > 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. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: x11-toolkits/xview (actually contool)
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
the most basic function of xview, it might be best to mark it as
BROKEN for the time being and complain with Xorg about yet another
case of backwards compatibility failing. Of course I meant to say
to patch it or remove the port and it's dependants.
[1] Patch:
Index: Makefile
===
RCS file: /home/ncvs/ports/sysutils/contool/Makefile,v
retrieving revision 1.20
diff -u -r1.20 Makefile
--- Makefile9 Jun 2009 15:33:17 - 1.20
+++ Makefile6 Aug 2009 05:20:11 -
@@ -24,8 +24,12 @@
MAN1= contool.1
+
pre-install:
@${MKDIR} ${PREFIX}/lib/help
+.if defined(WITH_DEBUG)
+ -${SED} -i.bak -e 's/INSTPGMFLAGS = -s/INSTPGMFLAGS =/'
${WRKSRC}/Makefile
+.endif
post-install:
@${CAT} ${PKGMESSAGE}
--
Mel
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: x11-toolkits/xview (actually contool)
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) gdb log attached -- This .signature sanitized for your protection $ gdb /usr/local/bin/contool contool.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd"...(no debugging symbols found)... Core was generated by `contool'. Program terminated with signal 6, Aborted. Reading symbols from /usr/local/lib/libxview.so.3...done. Loaded symbols for /usr/local/lib/libxview.so.3 Reading symbols from /usr/local/lib/libolgx.so.3...done. Loaded symbols for /usr/local/lib/libolgx.so.3 Reading symbols from /usr/local/lib/libXext.so.6...done. Loaded symbols for /usr/local/lib/libXext.so.6 Reading symbols from /usr/local/lib/libX11.so.6...done. Loaded symbols for /usr/local/lib/libX11.so.6 Reading symbols from /lib/libc.so.7...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/local/lib/libxcb.so.2...done. Loaded symbols for /usr/local/lib/libxcb.so.2 Reading symbols from /usr/local/lib/libXdmcp.so.6...done. Loaded symbols for /usr/local/lib/libXdmcp.so.6 Reading symbols from /usr/lib/librpcsvc.so.5...done. Loaded symbols for /usr/lib/librpcsvc.so.5 Reading symbols from /usr/local/lib/libXau.so.6...done. Loaded symbols for /usr/local/lib/libXau.so.6 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x283e48c7 in kill () at kill.S:3 3 RSYSCALL(kill) (gdb) bt #0 0x283e48c7 in kill () at kill.S:3 #1 0x283e4826 in __raise (s=6) at /usr/local/src/lib/libc/gen/raise.c:46 #2 0x283e342a in abort () at /usr/local/src/lib/libc/stdlib/abort.c:65 #3 0x283c98f6 in __assert (func=0x6 , file=0x5 , line=0, failedexpr=0x28298178 "ret != inval_id") at /usr/local/src/lib/libc/gen/assert.c:54 #4 0x2822d2ba in _XAllocID (dpy=0x28523600) at xcb_io.c:378 #5 0x281611b5 in server_init (parent=0, server_public=676349152, avlist=0xbfbfdc84) at server.c:746 #6 0x281b2a9d in xv_create_avlist (parent=0, pkg=0x281cb360, avlist=0xbfbfdc84) at xv.c:391 #7 0x281b2c6f in xv_create (parent=0, pkg=0x281cb360) at xv.c:307 #8 0x281b4924 in xv_init (attr1=1241974786) at xv_init.c:308 #9 0x0804b801 in ?? () #10 0x4a070802 in ?? () #11 0xbfbfea70 in ?? () #12 0xbfbfea90 in ?? () #13 0x in ?? () #14 0x in ?? () #15 0x in ?? () #16 0x in ?? () #17 0x in ?? () #18 0x in ?? () #19 0x in ?? () #20 0xbfbfea90 in ?? () #21 0xbfbfea70 in ?? () #22 0x in ?? () #23 0x in ?? () #24 0x in ?? () #25 0x in ?? () #26 0x in ?? () #27 0x in ?? () #28 0x in ?? () #29 0x in ?? () #30 0x in ?? () #31 0x in ?? () #32 0x in ?? () #33 0x in ?? () #34 0x in ?? () #35 0x in ?? () #36 0x in ?? () #37 0x in ?? () #38 0x in ?? () #39 0x in ?? () #40 0x in ?? () #41 0x in ?? () #42 0x in ?? () #43 0x in ?? () #44 0x in ?? () #45 0x in ?? () #46 0x in ?? () #47 0x in ?? () #48 0x in ?? () #49 0x in ?? () ---Type to continue, or q to quit--- #50 0x in ?? () #51 0x in ?? () #52 0x in ?? () #53 0x in ?? () #54 0x in ?? () #55 0x in ?? () #56 0x in ?? () #57 0x in ?? () #58 0x in ?? () #59 0x in ?? () #60 0x in ?? () #61 0x in ?? () #62 0x in ?? () #63 0x in ?? () #64 0x in ?? () #65 0x in ?? () #66 0x in ?? () #67 0x in ?? () #68 0x in ?? () #69 0x in ?? () #70 0x in ?? () #71 0x in ?? () #72 0x in ?? () #73 0x in ?? () #74 0x in ?? () #75 0x in ?? () #76 0x in ?? () #77 0x in ?? () #78 0x in ?? () #79 0x in ?? () #80 0x in ?? () #81 0x in ?? () #82 0x in ?? () #83 0x in ?? () #84 0x in ?? () #85 0x in ?? () #86 0x in ?? () #87 0x in ?? () #88 0x in ?? () #89 0x in ?? () #90 0x in ?? () #91 0x in ?? () #92 0x in ?? () #93 0x in ?? () #94 0x in ?? () #95 0x in ?? () #96 0x in ?? () #97 0x in ?? () #98 0x in ?? () #99 0x in ?? () #100 0x in ?? () #101 0x in ?? () #102 0x in ?? () #103 0x in ?? () #104 0x in ?? () ---Type to continue, or q to quit--- #105 0x000
Re: x11-toolkits/xview (actually contool)
Tom Uffner wrote: > Doug Barton wrote: >> I thought contool looked interesting so I tried build it. It requires >> xview, which fails as follows on a fairly recent -current (8.0-BETA2 >> r195917: Mon Jul 27 16:09:24 PDT 2009): > > i posted an ugly workaround for this a few days ago, which started this > thread, and Mel Flynn replied with a better one. Ok, committed, thanks! -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: x11-toolkits/xview (actually contool)
Doug Barton wrote: I thought contool looked interesting so I tried build it. It requires xview, which fails as follows on a fairly recent -current (8.0-BETA2 r195917: Mon Jul 27 16:09:24 PDT 2009): i posted an ugly workaround for this a few days ago, which started this thread, and Mel Flynn replied with a better one. tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: x11-toolkits/xview (actually contool)
Carlos A. M. dos Santos wrote: > On Wed, Aug 5, 2009 at 5:50 PM, Tom Uffner wrote: >> Carlos A. M. dos Santos wrote: >> >>> Can't xconsole do the job for you instead of contool? >> more or less. i am using xconsole by default. however i prefer contool >> because it has the following features which are missing from every other >> X console program that I am aware of: >> >> 1. it can remain iconified (or entirely unmapped) and out of my way most >> of the time. >> 2. it can timestamp the messages it prints >> 3. it can alert me to the presence of new console messages by flashing >> its icon, beeping, and/or opening its window >> 4. it allows me to specify, using regular expression filters, the types >> of messages it should or should not alert on. >> >>> BTW, what problems do you have with contool? Are they the same ones >>> discussed before in these threads? >>> >>> >>> http://lists.freebsd.org/pipermail/freebsd-hackers/2008-October/026516.html >>> >>> http://lists.freebsd.org/pipermail/freebsd-hackers/2008-November/026722.html >> my xconsole still exhibits those problems. don't know about contool yet. > > It is even worst on 8.0, now. Even making xconsole SUID root I can't > see any of the messages written to /dev/console. Using "xterm -C" does > not work. > >> as i said, i haven't had the time to diagnose it yet. what console i use >> on my X workstations is not really that high a priority in the grand scheme >> of things. contool is exiting with this message: >> >> Assertion failed: (ret != inval_id), function _XAllocID, file xcb_io.c, line >> 378. >> Abort >> >> which may be another symptom of the tty layer changes, but i haven't really >> had time to look at it yet. > > Looks like a bug in XCB. This would not be a surprise, given the poor > engineering of Xorg these days (lack of it, in fact). Try rebuilding > libX11 with the patch I sent in this PR: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=137373 > > You will not miss XCB. It is as useful as hole int your head. I thought contool looked interesting so I tried build it. It requires xview, which fails as follows on a fairly recent -current (8.0-BETA2 r195917: Mon Jul 27 16:09:24 PDT 2009): cc -fPIC -O2 -pipe -ggdb -fno-strict-aliasing -ggdb -I../../../build/include -I/usr/local/include-DCSRG_BASED -I/include -DSUNOS41 -DX11R6 -DFUNCPROTO=15 -DNARROWPROTO -DOS_HAS_LOCALE -DOS_HAS_MMAP -DEXTRASMENU="\"/usr/local/lib/.text_extras_menu\"" -I../../../build/include -I/usr/local/include-DCSRG_BASED -I/include -DSUNOS41 -DX11R6 -DFUNCPROTO=15 -DNARROWPROTO -DOS_HAS_LOCALE -DOS_HAS_MMAP -DEXTRASMENU="\"/usr/local/lib/.text_extras_menu\"" -c ps_impl.c -o shared/ps_impl.o ps_impl.c: In function 'ps_create': ps_impl.c:183: warning: passing argument 1 of 'xv_error' makes integer from pointer without a cast rm -f ev_display.o shared/ev_display.o cc -fPIC -O2 -pipe -ggdb -fno-strict-aliasing -ggdb -I../../../build/include -I/usr/local/include-DCSRG_BASED -I/include -DSUNOS41 -DX11R6 -DFUNCPROTO=15 -DNARROWPROTO -DOS_HAS_LOCALE -DOS_HAS_MMAP -DEXTRASMENU="\"/usr/local/lib/.text_extras_menu\"" -I../../../build/include -I/usr/local/include-DCSRG_BASED -I/include -DSUNOS41 -DX11R6 -DFUNCPROTO=15 -DNARROWPROTO -DOS_HAS_LOCALE -DOS_HAS_MMAP -DEXTRASMENU="\"/usr/local/lib/.text_extras_menu\"" -c ev_display.c -o shared/ev_display.o In file included from ../../../build/include/xview_private/tty_impl.h:216, from ev_display.c:36: /usr/include/sys/ioctl_compat.h:42:2: error: #error "Definitions not available without TTY ioctl compat." ev_display.c: In function 'ev_init_X_carets': ev_display.c:89: warning: passing argument 1 of 'xv_error' makes integer from pointer without a cast ev_display.c: In function 'ev_put_caret': ev_display.c:138: warning: passing argument 1 of 'xv_error' makes integer from pointer without a cast *** Error code 1 -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: x11-toolkits/xview (actually contool)
On Wed, Aug 5, 2009 at 5:50 PM, Tom Uffner wrote: > Carlos A. M. dos Santos wrote: > >> Can't xconsole do the job for you instead of contool? > > more or less. i am using xconsole by default. however i prefer contool > because it has the following features which are missing from every other > X console program that I am aware of: > > 1. it can remain iconified (or entirely unmapped) and out of my way most > of the time. > 2. it can timestamp the messages it prints > 3. it can alert me to the presence of new console messages by flashing > its icon, beeping, and/or opening its window > 4. it allows me to specify, using regular expression filters, the types > of messages it should or should not alert on. > >> BTW, what problems do you have with contool? Are they the same ones >> discussed before in these threads? >> >> >> http://lists.freebsd.org/pipermail/freebsd-hackers/2008-October/026516.html >> >> http://lists.freebsd.org/pipermail/freebsd-hackers/2008-November/026722.html > > my xconsole still exhibits those problems. don't know about contool yet. It is even worst on 8.0, now. Even making xconsole SUID root I can't see any of the messages written to /dev/console. Using "xterm -C" does not work. > as i said, i haven't had the time to diagnose it yet. what console i use > on my X workstations is not really that high a priority in the grand scheme > of things. contool is exiting with this message: > > Assertion failed: (ret != inval_id), function _XAllocID, file xcb_io.c, line > 378. > Abort > > which may be another symptom of the tty layer changes, but i haven't really > had time to look at it yet. Looks like a bug in XCB. This would not be a surprise, given the poor engineering of Xorg these days (lack of it, in fact). Try rebuilding libX11 with the patch I sent in this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=137373 You will not miss XCB. It is as useful as hole int your head. -- 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. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: x11-toolkits/xview (actually contool)
Carlos A. M. dos Santos wrote: Can't xconsole do the job for you instead of contool? more or less. i am using xconsole by default. however i prefer contool because it has the following features which are missing from every other X console program that I am aware of: 1. it can remain iconified (or entirely unmapped) and out of my way most of the time. 2. it can timestamp the messages it prints 3. it can alert me to the presence of new console messages by flashing its icon, beeping, and/or opening its window 4. it allows me to specify, using regular expression filters, the types of messages it should or should not alert on. BTW, what problems do you have with contool? Are they the same ones discussed before in these threads? http://lists.freebsd.org/pipermail/freebsd-hackers/2008-October/026516.html http://lists.freebsd.org/pipermail/freebsd-hackers/2008-November/026722.html my xconsole still exhibits those problems. don't know about contool yet. as i said, i haven't had the time to diagnose it yet. what console i use on my X workstations is not really that high a priority in the grand scheme of things. contool is exiting with this message: Assertion failed: (ret != inval_id), function _XAllocID, file xcb_io.c, line 378. Abort which may be another symptom of the tty layer changes, but i haven't really had time to look at it yet. tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
