On Tue, Oct 12, 2021 at 10:31 AM Omar Polo <o...@omarpolo.com> wrote: > readline from ports shouldn't be needed. Moreover, port's readline > install files as `libereadline', so it should be difficult to pick those > header by accident.
Since I'm curious, what if a program needs newer readline? It will need libereadline therefore in the headers, right? > # pkg_add gdb > $ egdb $(which pspg) pspg.core seems the same stack trace to me (I produced a new core file): puffy# egdb $(which pspg) pspg.core GNU gdb (GDB) 7.12.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-openbsd6.9". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/local/bin/pspg...done. [New process 557312] Core was generated by `pspg'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0000000000000000 in ?? () (gdb) bt #0 0x0000000000000000 in ?? () #1 0x00000bd4557bf1b6 in _rl_callback_newline () at /usr/src/gnu/lib/libreadline/callback.c:75 #2 rl_callback_handler_install (prompt=<optimized out>, linefunc=0xbd162b99b50 <readline_callback>) at /usr/src/gnu/lib/libreadline/callback.c:93 #3 0x00000bd162b996b4 in get_string (prompt=0xbd162b68c53 "/", buffer=0x7f7ffffe4e30 "\t", maxsize=255, defstr=0xbd162bac860 <last_row_search> "", _tabcomplete_mode=<optimized out>) at src/readline.c:588 #4 0x00000bd162b8a2d8 in main (argc=0, argv=0x1) at src/pspg.c:5405 Any other thing I can do to better diagnose the problem? Thanks, Luca
