[issue] Crash at startup

[Mike Kupfer]

>>>>> "ST" == Stephen J Turnbull <stephen at xemacs.org> writes:

ST> However I suspect that this is an Xlib bug on the Sun.

MikeK> Could be.  When I get a chance I'll look for likely looking entries
MikeK> in the bug database.

I did a search on XRegisterIMInstantiateCallback and found a couple
bugs, both of which were marked as fixed in, or prior to, Solaris 10.

FWIW, both bugs were apparently tickled by not having the XIM server up
and running.  (I don't know much about XIM--one of the bugs listed
htt_xbe, htt_server, and atok8 as likely XIM servers.)

ST> Would you take a look at the "Platform" popup (click the '(list)'
ST> link) on the tracker (doesn't matter which issue), and let me know
ST> if you think it would be worth adding "sparc" as CPU and/or
ST> "solaris" as OS to that list?

ST> For context, assume that if we do add them, we'll end up with maybe
ST> a dozen CPUs and two or three dozen OSes,

The only compelling reason I can think of to do that would be if
somebody were regularly looking for issues that are appearing on a
particular platform.  Given my current time constraints, I'm not likely
to check here regularly for Solaris issues.  Though I won't object if
someone adds me to the Nosy list for issues that could be
Solaris-specific (on any hardware).

ST> and that not all that many users will set them properly (although in
ST> theory it would be possible to use Installation information to do it
ST> automatically, I don't see it happening soon).

Yeah, I don't have a good suggestion for that.  Sun's internal database
has a separate State to distinguish totally new bugs from ones where the
category and priority have been sanity-checked.  I tend to think that's
more complexity than we need for XEmacs.

cheers,
mike