On Fri, Aug 03, 2007 at 03:19:57PM +0400, Alexandra N. Kossovsky wrote: > On Thu, Aug 02, 2007 at 05:08:53PM -0400, Thomas Dickey wrote: > > If you have the time, compiling the xterm source (with the appropriate > > options to match Debian's configuration) could perhaps get a usable > > walkback from the debugger. I can offer advice on that... > > I've got "apt-get source xterm" and re-compiled it (with debug > information). See below for the output. Tell me if you need more info.
ok - see notes
> Breakpoint 1, xerror (d=0x55f450, ev=0x7fff950c4fb0) at ./misc.c:3279
> 3279 {
> (gdb) bt
> #0 xerror (d=0x55f450, ev=0x7fff950c4fb0) at ./misc.c:3279
> #1 0x00002b87164a806e in _XError (dpy=0x55f450, rep=<value optimized out>)
> at ../../src/XlibInt.c:2888
> #2 0x00002b87164a9dbb in _XReply (dpy=0x55f450, rep=0x7fff950c5120, extra=0,
> discard=1) at ../../src/XlibInt.c:1817
> #3 0x00002b8716496c7b in XParseColor (dpy=0x55f450, cmap=32, spec=0x56d0e0
> "blue",
> def=0x7fff950c5180) at ../../src/ParseCol.c:126
...from here down (#3..#0) is in the X libraries.
> #4 0x0000000000424007 in AllocateAnsiColor (xw=0x578970, res=0x57a800,
> spec=0x18b <Address 0x18b out of bounds>) at ./misc.c:1668
This is interesting, but the line-number doesn't match my source for #222.
That's from lines 1473 to 1508. Either there's something wrong with the
line-numbering, or the parameter for spec is broken. It would be simple
to add a printf in xterm at the beginning of this function to verify both:
fprintf(stderr, "AllocateAnsiColor spec=%p\n", spec);
fprintf(stderr, "->'%s'\n", spec);
If it's really a broken parameter, the first fprintf will work, and it'll
die right away on the second.
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
pgp0d3j6NHEuP.pgp
Description: PGP signature
