[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #25525] Segfault using goops

From: Stefan Israelsson Tampe
Subject: [bug #25525] Segfault using goops
Date: Fri, 16 Apr 2010 11:26:08 +0000
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv: Gecko/20100316 Firefox/3.6.2

Follow-up Comment #2, bug #25525 (project guile):

The reason is that code assume cpl to be a null terminated list but it's not
due to the bug, then a cdr will make the crash. Now this is a symptom and not
the cause. But we can avoid a segmentation fault by making sure that we check
for a pair although it will slow down the algorithm a little. Checking for a
pairs and silently move on if error yield an error in a layout check!

Better to fix the cause, right? Well to raise a question. by coding for
efficiency and assume that the code will be used correctly we will gain speed.
On the other hand this means that 
any bug will, with maybe to high probability, crash the repl.

I would prefere to use fast and unsecure paths only for proven
datastructures. Or, next best, use checks that is on only under a debug


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]