Re: 13.0-RC3 bison causes tputs SIGSEGV

2021-04-03 Thread Thomas Dickey
On Sat, Apr 03, 2021 at 02:36:29PM -0400, Thomas Dickey wrote: ... attaching trace :-) -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net TRACING NCURSES version 6.2.20210403 (tracelevel=0x) called {setupterm("screen",2,0x7fffe2b0) your terminal name is scree

Re: 13.0-RC3 bison causes tputs SIGSEGV

2021-04-03 Thread Thomas Dickey
On Wed, Mar 31, 2021 at 07:54:09PM -0400, Thomas Dickey wrote: > On Wed, Mar 31, 2021 at 06:49:55PM -0400, Thomas Dickey wrote: > > On Wed, Mar 31, 2021 at 09:40:49PM +0200, Juraj Lutter wrote: > > > > > > > On 31 Mar 2021, at 15:53, Henric Jungheim wrote: > > > > > > > >> > > > >> Knowing that

Re: 13.0-RC3 bison causes tputs SIGSEGV

2021-03-31 Thread Thomas Dickey
On Wed, Mar 31, 2021 at 06:49:55PM -0400, Thomas Dickey wrote: > On Wed, Mar 31, 2021 at 09:40:49PM +0200, Juraj Lutter wrote: > > > > > On 31 Mar 2021, at 15:53, Henric Jungheim wrote: > > > > > >> > > >> Knowing that would help me see whether the problem is faulty > > >> initialization > > >

Re: 13.0-RC3 bison causes tputs SIGSEGV

2021-03-31 Thread Thomas Dickey
On Wed, Mar 31, 2021 at 09:40:49PM +0200, Juraj Lutter wrote: > > > On 31 Mar 2021, at 15:53, Henric Jungheim wrote: > > > >> > >> Knowing that would help me see whether the problem is faulty initialization > >> from libtextstyle (i.e., the SCREEN pointer is null, making the path via > >> the s

Re: 13.0-RC3 bison causes tputs SIGSEGV

2021-03-31 Thread Juraj Lutter
> On 31 Mar 2021, at 15:53, Henric Jungheim wrote: > >> >> Knowing that would help me see whether the problem is faulty initialization >> from libtextstyle (i.e., the SCREEN pointer is null, making the path via >> the static structure), or some ifdef-combination in ncurses that I've >> neglecte

Re: 13.0-RC3 bison causes tputs SIGSEGV

2021-03-31 Thread Henric Jungheim
On Tue, Mar 30, 2021 at 08:48:03PM -0400, Thomas Dickey wrote: > On Tue, Mar 30, 2021 at 08:37:22AM +0200, Juraj Lutter wrote: > > Hi, > > > > very similar behavior is observed in editors/poke, on recent 13.0-STABLE > > (stable/13-85ad493677a2): > > > > (lldb) bt > > * thread #1, name = 'poke',

Re: 13.0-RC3 bison causes tputs SIGSEGV

2021-03-31 Thread Juraj Lutter
> On 31 Mar 2021, at 15:53, Henric Jungheim wrote: > >> >> So... the question I have is what is $TERM in this case, >> and where is the related terminal description (in terminfo or termcap). > > In the example in my original email, $TERM was "xterm-256color" > (connected through "Windows Term

Re: 13.0-RC3 bison causes tputs SIGSEGV

2021-03-30 Thread Thomas Dickey
On Tue, Mar 30, 2021 at 08:37:22AM +0200, Juraj Lutter wrote: > Hi, > > very similar behavior is observed in editors/poke, on recent 13.0-STABLE > (stable/13-85ad493677a2): > > (lldb) bt > * thread #1, name = 'poke', stop reason = signal SIGSEGV: invalid address > (fault address: 0x0) > * fra

Re: 13.0-RC3 bison causes tputs SIGSEGV

2021-03-29 Thread Juraj Lutter
Hi, very similar behavior is observed in editors/poke, on recent 13.0-STABLE (stable/13-85ad493677a2): (lldb) bt * thread #1, name = 'poke', stop reason = signal SIGSEGV: invalid address (fault address: 0x0) * frame #0: 0x frame #1: 0x0008009ed30a libncursesw.so.9`del

Re: 13.0-RC3 bison causes tputs SIGSEGV

2021-03-29 Thread Thomas Dickey
On Mon, Mar 29, 2021 at 12:12:55PM -0700, Henric Jungheim wrote: > > I ran into a bit of an odd problem when building the > sysutils/grub2-bhyve port on 13.0-RC3 (on x64). The bison command > dumps core when the output is going to a console. Redirecting the > build output to a file avoids the pro

13.0-RC3 bison causes tputs SIGSEGV

2021-03-29 Thread Henric Jungheim
I ran into a bit of an odd problem when building the sysutils/grub2-bhyve port on 13.0-RC3 (on x64). The bison command dumps core when the output is going to a console. Redirecting the build output to a file avoids the problem. I'm not sure if this is an ncurses issue, a port issue (and which