[Top][All Lists]

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

Re: Segment Fault of newterm in ncurses-6.1_p20190609

From: Thomas Dickey
Subject: Re: Segment Fault of newterm in ncurses-6.1_p20190609
Date: Sat, 17 Aug 2019 13:21:07 -0400
User-agent: NeoMutt/20170113 (1.7.2)

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:


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:


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).

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

Thomas E. Dickey <address@hidden>

Attachment: valgrind.log
Description: Text document

Attachment: signature.asc
Description: PGP signature

reply via email to

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