[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LYNX-DEV weird crashes
From: |
Foteos Macrides |
Subject: |
Re: LYNX-DEV weird crashes |
Date: |
Sat, 17 May 1997 20:55:08 -0500 (EST) |
address@hidden (Larry W. Virden, x2487) wrote:
>Current function is FatalProblem
> 2239 abort();
>(dbx 1) where
> [1] pthread_mutexattr_setprotocol(0x27, 0x27, 0xb, 0x1b0a88, 0xefffcb7c,
> 0x1), at 0xef634144
>=>[2] FatalProblem(sig = 11), line 2239 in "LYMain.c"
> ---- called from signal handler with signal 11 (SIGSEGV) ------
> [3] LYno_attr_char_case_strstr(chptr = 0xa "",
^^^^^^^^^^^^^^
> tarptr = 0xefffd9c4 "seven l"), line 762 in "LYStrings.c"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>[...]
I took Klaus' word for it that there's no hidden problem to
worry about with the native solaris compiler, but what does that
[3] entry mean? I had interpretted it to mean that you had an
obsolete but still valid links[i].form structure for an INPUT
that had no VALUE="foo" attribute, and thus had it set to a
zero-length string, which was still valid, too, in the obsolete
links[i].forms->value element of the obsolute links[i].forms
structure. So what's the right way to interpret those dbx
outputs?
Fote
=========================================================================
Foteos Macrides Worcester Foundation for Biomedical Research
address@hidden 222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================
;
; To UNSUBSCRIBE: Send a mail message to address@hidden
; with "unsubscribe lynx-dev" (without the
; quotation marks) on a line by itself.
;
- Re: LYNX-DEV weird crashes, (continued)
- Re: LYNX-DEV weird crashes, Foteos Macrides, 1997/05/17
- Re: LYNX-DEV weird crashes, Foteos Macrides, 1997/05/17
- Re: LYNX-DEV weird crashes,
Foteos Macrides <=
- Re: LYNX-DEV weird crashes, Foteos Macrides, 1997/05/17
- Re: LYNX-DEV weird crashes, Foteos Macrides, 1997/05/18