[prev in list] [next in list] [prev in thread] [next in thread] 

List:       netbsd-current-users
Subject:    Re: gdb crashes on current
From:       Brett Lymn <blymn () internode ! on ! net>
Date:       2024-03-21 6:27:17
Message-ID: ZfvQdcsjbcKBepDC () internode ! on ! net
[Download RAW message or body]

On Wed, Mar 20, 2024 at 10:02:41PM +0000, Patrick Welche wrote:
> 
> Just had a go, and "tui enable" doesn't get as far as libcurses
> 

How odd.  I tried this on my system which was last updated June 14 last
year and both running gdb then doing tui enable or just running gdb -tui
Just Works(tm).

I have gdb:

GNU gdb (GDB) 11.0.50.20200914-git

I guess I will have to update and see what happens.

> 
> but "gdb -tui" does:
> 
> Thread 1 "" received signal SIGSEGV, Segmentation faultprefresh (pad=0x0, pbegy=0, \
> pbegx=0, sbegy=1, sbegx=5, smaxy=0, smaxx=78) at \
> /usr/src/lib/libcurses/refresh.c:511 511             pad->pbegy = pbegy;
> (gdb) bt
> #0  prefresh (pad=0x0, pbegy=0, pbegx=0, sbegy=1, sbegx=5, smaxy=0, smaxx=78)
> at /usr/src/lib/libcurses/refresh.c:511

Pad being NULL is a Bad Thing.  That variable should contain a pointer
to a WINDOW structure.

-- 
Brett Lymn
--
Sent from my NetBSD device.

"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"


[prev in list] [next in list] [prev in thread] [next in thread]