On Sat, May 06, 2017 at 09:45:22PM +0200, Carsten Kunze wrote:

> Hello,
> 
> I am not on this mailing list and I am not able to debug the following issue. 
>  It is just for information since a segmentation fault may be an issue on a 
> OpenBSD base system library.  The system I am using is very old (Oct. 2016) 
> but ncurses likely does not have changed much since then:
> 
> OpenBSD 6.0-current (GENERIC) #2384: Fri Oct 14 00:06:17 MDT 2016
> 
> What I am trying to do is to display UTF-8 chars using wadd_wchnstr().  Then 
> it crashes in lib_addstr.c:186 (I don't have the source).
> 
> If this is not relevant, just ignore the mail and sorry for the noise.
> 
> Program received signal SIGSEGV, Segmentation fault.                          
>                                                                               
>                                     
> wadd_wchnstr (win=0x15c8a6049a00, astr=0x15c664e47e28, n=4) at 
> /usr/src/lib/libcurses/base/lib_addstr.c:186                                  
>                                                    
> 186     /usr/src/lib/libcurses/base/lib_addstr.c: No such file or directory.  
>                                                                               
>                                     
>         in /usr/src/lib/libcurses/base/lib_addstr.c                           
>                                                                               
>                                     
> (gdb) bt                                                                      
>                                                                               
>                                     
> #0  wadd_wchnstr (win=0x15c8a6049a00, astr=0x15c664e47e28, n=4) at 
> /usr/src/lib/libcurses/base/lib_addstr.c:186                                  
>                                                
> #1  0x000015c664c20f56 in putmbs (w=0x15c8a6049a00, s=0x15c885e05100 
> "�\207İ", n=4) at ui2.c:1287                                                  
>                                              
> 
> ... following trace is not relevant.

Too little information. First check if it is still there in current
src, if so then try to come up with a little program that exposes the
bug.

BTW, soources are freely avaialble,

        -Otto

Reply via email to