On 2/6/19 10:31 PM, Dennis Clarke wrote:
>
> This has been tricky to isolate but after building and trying bash 5.0.2
> and then bash 4.4.23 I get the exact same sigsegv in the same place with
> both :
I can't reproduce this on Solaris 10 in VirtualBox with bash4.4 or
bash-5.0.
>
> dclarke@corv_$ dbx
> /usr/local/build/bash-4.4.18-023_SunOS5.10_sparc64vii+.001/bash
> Reading bash
> Reading ld.so.1
> Reading libreadline.so.8
> Reading libhistory.so.8
> Reading libcurses.so.1
> Reading libintl.so.8.1.5
> Reading libiconv.so.2.6.0
> Reading libc.so.1
> Reading libsocket.so.1
> Reading libnsl.so.1
> Reading libdl.so.1
> (dbx) run
> Running: bash
> (process id 19243)
> Reading libc_psr.so.1
> signal SEGV (no mapping at the fault address) in strcpy at 0xffffffff7e13c2e8
> 0xffffffff7e13c2e8: strcpy+0x00e8: ldx [%o2 + %o3], %o1
> Current function is get_term_capabilities
You could try setting a breakpoint here and seeing which termcap
capability it's looking for when it gets the segv. Maybe the buffer
is too small (it's 2K) to hold all the string capabilities of the
terminal emulation you're using.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU [email protected] http://tiswww.cwru.edu/~chet/
_______________________________________________
Bug-readline mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-readline
