Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]tlug: Re: kinput2+canna problem (plus unrelated
- To: tlug@example.com
- Subject: tlug: Re: kinput2+canna problem (plus unrelated
- From: "Stephen J. Turnbull" <turnbull@example.com>
- Date: Wed, 19 May 1999 17:10:13 +0900 (JST)
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <374252CA.A38ACF8B@example.com>
- References: <199905180732.QAA08143@example.com><374252CA.A38ACF8B@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
>>>>> "John" == John Seebach <jseebach@example.com> writes: John> Still, even with all of the gnome stuff gone, kinput2 does John> some wacky stuff. For example, if it's running, several John> programs segfault when I try to start them. Among them John> xterm, xemacs (with mule and canna support), and a number of John> others. Actually, most everything else. Any ideas as to why John> this might be or where I should look? Well, if you were using the nicer on-the-spot or over-the-spot styles, XEmacs used to try to give a null window argument for the unused window to Xlib and Xlib would seppuku. This is an Xlib bug IMO (still unfixed, I think), and I wouldn't be surprised if it bit a lot of apps over the years. I think mostly they're fixed by now, though. If XEmacs is at least version 20.4 (should be), then that bug is fixed. This is touchy, difficult stuff, unfortunately. Both the standards and the implementations were written mostly carelessly[1] and in bad style. IMHO. Core dumps are almost always bugs, and there are far too many of them needing working around in this part of Xlib. We can hope you'll find an easy fix, but.... If you're game ... you can try `gdb xemacs' (or whatever---yes, it's possibly that bad that you have to haul out the heavy artillery), but it will probably just tell you you're crapping out in XOpenIM or XOpenIC; libX11.so probably doesn't have debugging info in it. What I would do is build kinput2 from the sources with debug-enabled and put it into debug mode, then watch what it's doing when things crap out. It's all great fun, definitely worth it, at least if you can take vacation from your day job to bone up on X and debug the input managers ;-) Footnotes: [1] Ie, so what if other parts of the system might break? -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 __________________________________________________________________________ __________________________________________________________________________ What are those two straight lines for? "Free software rules." ------------------------------------------------------------------- Next Nomikai: May 26 (Wed), 19:00 Tengu TokyoEkiMae 03-3275-3691 *** Special guest: Eric S. Raymond Next Technical Meeting: June 19 (Sat), 12:30 place: Temple Univ. Topic: Linux SMP and the Intel SC450NX Quad Xeon Server platform ------------------------------------------------------------------- more info: http://www.tlug.gr.jp Sponsor: Global Online Japan
- References:
- tlug: Re: kinput2+canna problem (plus unrelated
- From: John Seebach <jseebach@example.com>
Home | Main Index | Thread Index
- Prev by Date: tlug: Re: kinput2+canna problem (plus unrelated
- Next by Date: tlug: Nomikai attendance list.
- Prev by thread: tlug: Re: kinput2+canna problem (plus unrelated
- Next by thread: tlug: Nomikai attendance list.
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links