[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#329901: xterm freezes when starting mc



On Sun, Sep 25, 2005 at 04:50:14PM +0200, Jan Gorski wrote:
> On Sat, 24 Sep 2005 at 19:25:52 -0400, Thomas Dickey wrote:
> > (That would be "configure --enable-trace --enable-wide-chars --enable-luit",
> > and the executable produces Trace-parent.out and Trace-child.out)
> 
> Well, I've run it. Traces are in http://slimak.info/~slimak/traces.tar.bz2 if
> you want to look at them. All hangs end with this line

thanks (got a copy for reading)

> xtermGetColorRes for Acolors[x]
> 
> with different x.
> 
> I've noticed one more thing --- with default font mc starts without problems.
> I use *VT100*font: -xos4-terminus-bold-r-normal--24-240-72-72-c-120-iso10646-1
> 
> > Other than that - attaching gdb to the xterm process and doing a bt (stack
> > trace) should show where it is executing.
> 
> #0  0xb7c4cf58 in select () from /lib/tls/libc.so.6
> #1  0xb7ed962a in _XEnq () from /usr/X11R6/lib/libX11.so.6
> #2  0xb7ed9a3e in _XRead () from /usr/X11R6/lib/libX11.so.6
> #3  0xb7edaa2a in _XReply () from /usr/X11R6/lib/libX11.so.6
> #4  0xb7ecb3c6 in XParseColor () from /usr/X11R6/lib/libX11.so.6
> #5  0x0806a605 in AllocateAnsiColor (pTerm=0x80c2490, res=0x80c2628, 
> 	spec=0x80c062c "yellow") at ./misc.c:1421
> #6  0x0806a743 in xtermGetColorRes (res=0x80c2628) at ./misc.c:1451
> #7  0x08050ff3 in SGR_Foreground (color=11) at ./charproc.c:805
> #8  0x08051189 in setExtendedFG () at ./charproc.c:881
> #9  0x08057f32 in doparsing (c=Variable "c" is not available.) 
> 	at ./charproc.c:1915
> #10 0x08059621 in VTparse () at ./charproc.c:2770
> #11 0x08059725 in VTRun () at ./charproc.c:4667
> #12 0x08066be5 in main (argc=0, argv=0xbfaaf288) at ./main.c:2291
>     
> Does it make things clearer?

That sounds like some useful information.  xterm loads the color
information for resource-values once - the first time they're used.  But
you're running mc twice, and it's allocating colors.  iirc, mc uses
yellow in each screen.  So it sounds as if "once" is not correct (I'll
have to review that and see if I can guess why).

Why it would break for a particular font - I can't guess (though I
suppose it's possible that some logic error with fonts could cause the
program to modify the resource table - that's only speculation).

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

Attachment: pgpRxz4RAmV04.pgp
Description: PGP signature


Reply to: