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

Bug#256931: xterm not liking -sb -si while running in vncserver



On Tue, Jun 29, 2004 at 04:20:33PM -0700, Jeff Bowden wrote:
> >>$ xterm -sb
> >>xterm:  bad command line option "-sb"
> >>
> >>usage:  xterm [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] 
> >>[] []
> >>   [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [-C] [-Sccn]
> >>   
> >>
> >
> >I haven't seen this one before.  Can you get this behavior from the
> >command-line?  Looks like something's trashed memory (on startup, xterm
> >constructs the sorted help-message, but that's independent of the
> >resource computation - but the help-message is trashed).
> > 
> >
> 
> I'm not sure what you mean.  That *is* the behaviour I get from the 
> command line.

long day (I focused on the window manager but overlooked the command-line).
 
> I ran strace on it in both the broken and working configurations.  They 
> diverge at the point where the working configuration looks at a bunch of 
> locale files and the broken one doesn't.

What locale (environment) settings are you using?  Normally I'd expect
locale to be where something breaks.
 
> Let me know if there's any specific tests you want me to run.

If I were debugging it, I'd configure it with the traces
	configure --enable-trace
That might replicate the problem, or it might not, depending on whether this
is a build issue.  Without that - running it w/o setuid should let you
run ltrace on it.  There's one call to qsort (in the non-trace version).
All of those "[]" look like it's either run past the null on the end of
the table, or else it's picking up some non-printable text from somewhere.
(I wrote that a couple of years ago, so I thought it was fairly stable).

So an ltrace might show some clue of that - I think it's the simplest
thing to do.

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

Attachment: pgpsIu9yoSMAK.pgp
Description: PGP signature


Reply to: