On Fri, Aug 19, 2005 at 08:10:07PM +0200, Justin Pryzby wrote:
> clone 256376 -1
> reassign -1 xterm
> retitle -1 xterm: top in a super-small xterm crashes them both
> thanks
>
> Not only does top get SIGSEGV, so does the xterm in which it runs.
> Valgrind on a copy of xterm without SGID xterm reports lots of
> problems.
hmm - aside from the cosmetic issue you reported with libXt (an overlapping
memcpy is just that), what other warnings are you seeing with valgrind?
(and of course, what version of xterm, what size is "super-small", etc).
On Fri, Aug 19, 2005 at 08:10:07PM +0200, Justin Pryzby wrote:
> clone 256376 -1
> reassign -1 xterm
> retitle -1 xterm: top in a super-small xterm crashes them both
> thanks
>
> Not only does top get SIGSEGV, so does the xterm in which it runs.
> Valgrind on a copy of xterm without SGID xterm reports lots of
> problems.
hmm - aside from the cosmetic issue you reported with libXt (an overlapping
memcpy is just that), what other warnings are you seeing with valgrind?
(and of course, what version of xterm, what size is "super-small", etc).
-- invisible- island. net -island. net
Thomas E. Dickey
http://
ftp://invisible