Re: [Lynx-dev] SIGSEGV in scan_cookie_sublist

[Thomas Dickey]

On Sun, Mar 31, 2013 at 02:31:28PM +0000, Thorsten Glaser wrote:
> Thomas Dickey dixit:
> 
> >Is it something that you can reproduce without special data,
> >e.g., stuff that you cannot share?
> 
> I cannot reliably reproduce it at all, it just happens after
> a, usually very long (as in, days) time of browsing cookie-
> happy sites (fanfiction sites, in this case, mostly).

:-(

> I can do a debug build and save the core file next time, if
> you want. (Would be useful if the signal handler can be dis-
> abled, is there a compile-time option for that? Otherwise,
> gdb cannot inspect the stack frames beyond the handler.)

hmm - this option is helpful:

  -core             toggles forced core dumps on fatal errors (off)

.h2 NO_FORCED_CORE_DUMP
# Unix ONLY:
#===========
# If NO_FORCED_CORE_DUMP is set to TRUE, Lynx will not force
# core dumps via abort() calls on fatal errors or assert()
# calls to check potentially fatal errors.  The compilation
# default normally is FALSE, and can be changed here.  The
# compilation or configuration default can be toggled via
# the -core command line switch.
# Note that this setting cannot be used to prevent core dumps
# with certainty.  If this is important, means provided by the
# operating system or kernel should be used.
#
#NO_FORCED_CORE_DUMP:FALSE

(I don't see a clean way to disable the signal handlers).

-- 
Thomas E. Dickey <address@hidden>
http://invisible-island.net
ftp://invisible-island.net

signature.asc
Description: Digital signature