[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FAIL: test-term-ostream-xterm.sh
From: |
Jeffrey Walton |
Subject: |
Re: FAIL: test-term-ostream-xterm.sh |
Date: |
Mon, 15 Jun 2020 01:32:24 -0400 |
On Mon, Jun 15, 2020 at 1:20 AM Jeffrey Walton <noloader@gmail.com> wrote:
>
> On Sun, Jun 14, 2020 at 8:49 PM Bruno Haible <bruno@clisp.org> wrote:
> >
> > Hi Jeffrey,
> >
> > > I'm testing gettext-0.20.1 on an ODROID-XU4 with Ubuntu 18.04, fully
> > > patched.
> > >
> > > $ lsb_release -a
> > > Distributor ID: Ubuntu
> > > Description: Ubuntu 18.04.4 LTS
> > > Release: 18.04
> > > Codename: bionic
> > >
> > > $ uname -a
> > > Linux odroid 4.14.180-176 #1 SMP PREEMPT Tue May 19 00:40:55 -03 2020
> > > armv7l armv7l armv7l GNU/Linux
> >
> > I don't have that particular environment. But I have verified that on
> > Ubuntu 18.04 (x86_64), libtextstyle from gettext-0.20.2 passes its tests.
> > And that the output of 'infocmp -l -1 xterm' on my system is the same as
> > on yours.
> >
> > > FAIL: test-term-ostream-xterm.sh
> > > ================================
> > >
> > > Segmentation fault
> > > FAIL test-term-ostream-xterm.sh (exit status: 1)
> >
> > Could you please give additional info:
> >
> > 1) Can you get a gdb stack trace?
> > $ cd tests
> > $ TERM=xterm gdb ./test-term-ostream
> > or $ TERM=xterm ../libtool --mode=execute gdb ./test-term-ostream
> > (gdb) run > out1
> > (gdb) where
> >
> > 2) If that stack trace is not useful, then please rebuild the libtextstyle
> > directory (of gettext 0.20.2 if possible - that's the newest release)
> > with CFLAGS=-ggdb, and retry with gdb?
> >
> > Thanks.
>
> Thanks again Bruno.
>
> This may be a Ncurses problem. I build an updated Ncurses.
Yeah, this was an Ncurses/Termcap problem.
Ncurses is one of those libraries that is not easy to build. It
doesn't "just work" out of the box.
Jeff