bug-ncurses
[Top][All Lists]
Advanced

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

Re: Segment Fault of newterm in ncurses-6.1_p20190609


From: Han Han
Subject: Re: Segment Fault of newterm in ncurses-6.1_p20190609
Date: Mon, 19 Aug 2019 22:54:33 +0800



On Sun, Aug 18, 2019 at 1:21 AM Thomas Dickey <address@hidden> wrote:
On Sat, Aug 17, 2019 at 10:37:32AM -0400, Thomas Dickey wrote:
> On Sat, Aug 17, 2019 at 03:26:55PM +0800, Han Han wrote:
> > Versions:
> > ncurses-6.1_p20190609
> > gpm-1.20.7-r2
> > gdb-8.3
> > pinfo-0.6.13
>
> for context, Rawhide has these:
>
> ncurses-6.1-10.20180923.fc30.x86_64
> gpm-1.20.7-18.fc30.x86_64
> gdb-8.3-6.fc30.x86_64
> pinfo-0.6.10-20.fc29.x86_64

> > Steps:
> > It could be trigger by gdb or pinfo
> > I. for gdb:
> > # gdb -tui ls
> > [1]    3348 segmentation fault (core dumped)  gdb -tui ls
> >
> > II. for pinfo:
> > # pinfo close
> > Caught signal 11, bye!
> > pinfo: crash with: Success
>
> hmm - pinfo's easier to test (I'll focus on this).
>
> I don't see a clue regarding the terminal description used (i.e., $TERM).
>
> If I'd gotten a crash, the next step would be to run the application with
> valgrind to see if it could tell me anything.

I need more information to be able to reproduce the problem.
The configuration described is apparently not a Red Hat package build,
since it is not listed here:
Hello, my system is not Fedora or Redhat. It is gentoo. And the ncurses is build by
gcc-9.2.0. The configure of ncurses is:
./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --with-terminfo-dirs=/etc/terminfo:/usr/share/terminfo --enable-pc-files --with-pkg-config-libdir=/usr/lib64/pkgconfig --with-shared --without-hashed-db --without-ada --with-cxx --with-cxx-binding --with-cxx-shared --without-debug --without-profile --with-gpm=libgpm.so.1 --disable-term-driver --disable-termcap --enable-symlinks --with-rcs-ids --with-manpage-format=normal --enable-const --enable-colorfgbg --enable-hard-tabs --enable-echo --enable-warnings --without-assertions --enable-leaks --without-expanded --with-macros --with-progs --without-tests --without-trace --with-termlib --disable-stripping --disable-widec --without-pthread --without-reentrant --enable-overwrite

My terminal:
# echo $TERM
xterm-256color


https://apps.fedoraproject.org/packages/ncurses/builds/

If it had been, and if the problem was not resolved in the two months
since the cited patch, I should be able to reproduce it by the most
recent Fedora build.  Just to be sure, I rebuilt (in my rawhide machine)
this package:

https://koji.fedoraproject.org/koji/buildinfo?buildID=1348376
(ncurses-6.1-12.20190803.fc31).

and did the same for the current pinfo.  While valgrind shows me
some problems from pinfo, none of those are related to ncurses
(see attached log).
For the report of valgrind, see the attachment

fwiw, that's with TERM=xterm-256color, taking care to use the
corresponding ncurses-base and ncurses-term packages.

--
Thomas E. Dickey <address@hidden>
https://invisible-island.net
ftp://ftp.invisible-island.net


--
Best regards,
-----------------------------------
Han Han
Quality Engineer
Redhat.

Email: address@hidden
Phone: +861065339333

Attachment: pinfo.log
Description: Text Data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]