On Fri, Aug 03, 2007 at 11:40:57AM -0400, Thomas Dickey wrote:
> On Fri, Aug 03, 2007 at 07:22:09PM +0400, Alexandra N. Kossovsky wrote:
> > Hi.
> >
> > 1. The problem below with the "spoiled stack" does not have any common with
> >the xterm crash. I can fix the "spoiled stack" with 2-line pat
Hi.
1. The problem below with the "spoiled stack" does not have any common with
the xterm crash. I can fix the "spoiled stack" with 2-line patch in Xlib,
but it does not really help. Looks like an internal gdb problem,
really.
2. The problem is in X server. The problem exists with amd64
On Fri, Aug 03, 2007 at 05:18:13PM +0400, Alexandra N. Kossovsky wrote:
> On Fri, Aug 03, 2007 at 08:03:14AM -0400, Thomas Dickey wrote:
> > On Fri, Aug 03, 2007 at 03:19:57PM +0400, Alexandra N. Kossovsky wrote:
> > > Breakpoint 1, xerror (d=0x55f450, ev=0x7fff950c4fb0) at ./misc.c:3279
> > > 3279
On Fri, Aug 03, 2007 at 08:03:14AM -0400, Thomas Dickey wrote:
> On Fri, Aug 03, 2007 at 03:19:57PM +0400, Alexandra N. Kossovsky wrote:
> > Breakpoint 1, xerror (d=0x55f450, ev=0x7fff950c4fb0) at ./misc.c:3279
> > 3279{
> > (gdb) bt
> > #0 xerror (d=0x55f450, ev=0x7fff950c4fb0) at ./misc.c:32
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 fr
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"
On Thu, Aug 02, 2007 at 03:10:06PM +0200, Alexandra N. Kossovsky wrote:
> I can confirm this bug in Etch xterm (222-1etch2), amd64.
> Moreover, I can reproduce it!
I don't have etch (or amd64...), but have Debian/testing - and lots
of versions of xterm. With that combination, I'm not seeing the
p
I can confirm this bug in Etch xterm (222-1etch2), amd64.
Moreover, I can reproduce it!
The following command crashes xterm (and uxterm as well).
LANG=C LANGUAGE=en LC_CTYPE=ru_RU.UTF-8 LC_COLLATE=C vi xxx
(all locale variables not mentioned in the command line are C or POSIX)
xterm error message
8 matches
Mail list logo
