Geoff Wing writes:
> Mark White typed:
> :I've had rxvt falling over a lot under 1.5 - it dies when
> :I try to change font with:
> :    rxvt: XError: Request: 56 . 0, Error: 7
> 
> This is a BadFont error on XChangeGC() call, though most likely
> via a XSetFont() call.

Ok.  So, I just checked that all the fonts I asked for in
my .Xresources are legal, and they seem to be (I can do
    rxvt -fn xxx
for them, and it works).  I use lucida fonts for terminals.

Playing this evening, I discovered if I remove
    Rxvt.multichar_encoding:  noenc
resource [or do -km eucj, or something], it *does* manage to
change size on shift-(kp-plus) etc. (with suitable errors
telling me I haven't got EUCJ or SJIS versions of lucida -
they're all iso8859-1).  

However, the XError problem still occurs if I set all the
font resources to 7x14, and leave encoding as noenc.

> :and I've had it crash while editing or similar a number of
> :times, sig 4'ing during a free() operation.
> 
> Can you provide more information please?

Well, I have a core from the last time that happened, but
the stacktrace is unilluminating (at least to me :) -

    #0  0x805967d in dladdr ()
    #1  0x804c374 in dladdr ()
    #2  0x804e5c9 in dladdr ()
    #3  0x8050ac2 in dladdr ()
    #4  0x804b2e1 in free ()

They weren't very frequent, but generally once one terminal
crashed, all the others I had open would also do so within a
few operations, rather rapidly.  I've no idea if this is
related to the font problem; I wouldn't have though so.

I've used rxvt for many years without any crashes before I
switched to NetBSD (fairly recently), by the way!  So I was
fairly surprised...

> You're changing fonts via (alt|meta) and keypad (plus|minus)?

Shift-(kp-plus|kp-minus), yes.

> If you run from another window (or otherwise capture stderr)
> do you get any messages?

For the font change crash, there were no stderr messages.  I
don't *think* there were from the sig-4, either.

> What do you get from:
> % xrdb -query | egrep -i '^(rxvt|xterm)'

Well, quite a lot, because I've slightly adjusted all of the
colours a few shades darker!  But if I omit all those...
    Rxvt.font:      lucidasanstypewriter-12
    Rxvt.font1:     lucidasanstypewriter-10
    Rxvt.font2:     lucidasanstypewriter-10
    Rxvt.font3:     lucidasanstypewriter-14
    Rxvt.font4:     lucidasanstypewriter-18
    Rxvt.font5:     7x14
    Rxvt.font6:     10x20
    [...]
    Rxvt.termName:  xterm
    Rxvt.smallfont_key:     bracketleft
    Rxvt.bigfont_key:       bracketright
    Rxvt.scrollBar: false
    Rxvt.modifier:  mod1
    Rxvt.multichar_encoding:        noenc
as well as roughly the same for xterm.

> And from:
> % sh -c 'for I in -*-jisx0208* 7x14 6x10 6x13 8x13 8x16 10x20 12x24; do xlsfonts -fn $I; done'

gives, as we expected I guess, jis encoding for only fixed fonts:
    -jis-fixed-medium-r-normal--0-0-75-75-c-0-jisx0208.1983-0
    -jis-fixed-medium-r-normal--16-110-100-100-c-160-jisx0208.1983-0
    -jis-fixed-medium-r-normal--16-110-100-100-c-160-jisx0208.1983-0
    -jis-fixed-medium-r-normal--16-150-75-75-c-160-jisx0208.1983-0
    -jis-fixed-medium-r-normal--16-150-75-75-c-160-jisx0208.1983-0
    -jis-fixed-medium-r-normal--24-170-100-100-c-240-jisx0208.1983-0
    -jis-fixed-medium-r-normal--24-170-100-100-c-240-jisx0208.1983-0
    -jis-fixed-medium-r-normal--24-230-75-75-c-240-jisx0208.1983-0
    -jis-fixed-medium-r-normal--24-230-75-75-c-240-jisx0208.1983-0
    -misc-fixed-medium-r-normal--0-0-75-75-c-0-jisx0208.1983-0
    -misc-fixed-medium-r-normal--14-130-75-75-c-140-jisx0208.1983-0
    -misc-fixed-medium-r-normal--14-130-75-75-c-140-jisx0208.1983-0
    7x14   7x14
    6x10   6x10   6x10   6x10
    6x13   6x13   6x13   6x13
    8x13   8x13   8x13   8x13
    8x16   8x16
    10x20   10x20   10x20   10x20
    12x24   12x24   12x24   12x24
I've not adjusted the X font settings from the instalation
defaults AFAIK [I did reinstall from xsrc a while ago, but
the problem was happening both before and after that.]

> Most rxvt development these days is on NetBSD-current with XFree86 3.3.6
> under i386 class processors, 

...which is what I'm using.  Pretty much out of the box.  Hmm.  How odd.

> However, I still
> couldn't reproduce any errors even after hacking at the fonts.

Sorry to be awkward; thanks for your quick response.  Let me
know if I can provide more info.

Mark <><