SigCount assertion error when used with ferret-vis

Bug #1244346 reported by Mike Neish
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xgks (Ubuntu)
New
Undecided
Unassigned

Bug Description

When I try to do a "shade" plot from the ferret_c program (in ferret-vis_6.6.2-1), the program crashes during a call to the xgks library, with the message:
ferret_c: xevent.c:324: xProcessEvents: Assertion `SigCount > 0' failed.
Aborted (core dumped)

The ferret-vis source package ships with its own version of xgks (deprecated in favour of this system-wide xgks package). I noticed in the source of the ferret-vis version, someone had explicitly changed the assertion (I'm guessing to work around the same issue I'm having?):
    void
xProcessEvents()
{
    assert(SigCount > 0);
/* acm acm 9/12/2007 */
/* assert(SigCount > 0); */ <------
    assert(SigCount >= 0);
    ProcessEvents();
}

Applying this change to libxgks2 fixes the crash in ferret_c. I've attached a patch with the relevant changes.

Caveat: I'm treating this entire package as a black box, so I have no idea if this change will cause side-effects in other packages that use xgks.

$ lsb_release -rd
Description: Ubuntu 12.04.3 LTS
Release: 12.04

$ apt-cache policy libxgks2
libxgks2:
  Installed: 2.6.1-3
  Candidate: 2.6.1-3
  Version table:
 *** 2.6.1-3 0
        500 http://ca.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages
        100 /var/lib/dpkg/status

Tags: patch
Revision history for this message
Mike Neish (neishm) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "Patch to fix SigCount error when using xgks with ferret-vis" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.