vis segfault, Cudd_bddPickOneMinterm

From: Tobe Toben (tobe.toben_at_informatik.uni-oldenburg.de)
Date: Wed Sep 08 2004 - 13:16:33 MDT

• Next message: Fabio Somenzi: "Re: vis segfault, Cudd_bddPickOneMinterm"
• Previous message: Li, Lun: "when using Cudd_foreachCube to get a cube, what the order do the vars in cube follow, index or current level?"
• Next in thread: Fabio Somenzi: "Re: vis segfault, Cudd_bddPickOneMinterm"
• Reply: Fabio Somenzi: "Re: vis segfault, Cudd_bddPickOneMinterm"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

Dear vis community,

I encountered a segmentation fault after invoking the model_check
command. I've attachted the example, running 'vis < call' should
reproduce the bug with the current vis release.

A debug run reveals a null pointer returned by Cudd_bddPickOneMinterm in
file cuPort.c at line 4617. So the problem looks similiar to the bug
report of Laurent Arditi:

  http://vlsi.colorado.edu/~vis/vis-users/0157.html

Maybe one of the experts can have a look at this.

Thank you,
Tobe.

• APPLICATION/x-gtar attachment: vis_segf.tgz

• Next message: Fabio Somenzi: "Re: vis segfault, Cudd_bddPickOneMinterm"
• Previous message: Li, Lun: "when using Cudd_foreachCube to get a cube, what the order do the vars in cube follow, index or current level?"
• Next in thread: Fabio Somenzi: "Re: vis segfault, Cudd_bddPickOneMinterm"
• Reply: Fabio Somenzi: "Re: vis segfault, Cudd_bddPickOneMinterm"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

This archive was generated by hypermail 2.1.7 : Wed Sep 08 2004 - 13:23:47 MDT