gEDA-bug: [Bug 700448] Re: Poor reporting of schematic load errors

[Peter TB Brett <700448@xxxxxxxxxxxxxxxxxx>]

> The input parsing is bad enough it can die with a segfault (as in bug
832682).

Hi Krzysztof,

The issue in bug 832682 is *not* a segfault, it is an assertion failure,
as the backtrace supplied by the user clearly shows.

Although I agree that we should be detecting and handling these kinds of
problems in a more robust fashion, a segfault would be a much more
serious concern. All that bug demonstrates is that we are actually doing
input validation!

                                     Peter

** Changed in: geda
       Status: Confirmed => Triaged

** Changed in: geda
       Status: Triaged => In Progress

** Changed in: geda
     Assignee: (unassigned) => Eivind Kvedalen (eivind-z)

-- 
You received this bug notification because you are a member of gEDA Bug
Team, which is subscribed to gEDA.
https://bugs.launchpad.net/bugs/700448

Title:
  Poor reporting of schematic load errors

Status in GPL Electronic Design Automation tools:
  In Progress

Bug description:
  libgeda doesn't signal an error when a schematic or symbol file
  contains invalid syntax, or when any other load error is encountered.

  For example, gnetlist succeeds even when the input schematics
  specified contain unusable garbage.

  Steps to reproduce:

  ÂÂecho GARBAGE > test.sch;
  ÂÂif gnetlist -ggeda test.sch > /dev/null 2>/dev/null
  ÂÂthen
  ÂÂÂÂecho Succeeded
  ÂÂelse
  ÂÂÂÂecho Failed
  ÂÂfi

  Expected output:

  ÂÂFailed

  Actual output:

  ÂÂSucceeded

  Thanks to Peter Clifton for pointing out this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/geda/+bug/700448/+subscriptions


_______________________________________________
geda-bug mailing list
geda-bug@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-bug