Skip to Content.
Sympa Menu

cgal-discuss - [cgal-discuss] Problem with storing handles as member objects

Subject: CGAL users discussion list

List archive

[cgal-discuss] Problem with storing handles as member objects


Chronological Thread 
  • From: Costas Tsirogiannis <>
  • To:
  • Subject: [cgal-discuss] Problem with storing handles as member objects
  • Date: Mon, 5 Jul 2010 20:51:58 +0200
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=U5IcnWRwyd/Cvg55oUQTpeBDSU5Lz78gAbxc2klJx4ItN/z/eqx1M1sUuwysj61F+g ic035TkMz8B8n0t4Nh7uR3YMlAVBJgnxD0seVKbOSfTzGoBJtWFKIgECMZjwHJYBFV6T oA1Cn/SIibG5njVWnQfohNSYhmm4wrQztMQOI=

Greetings,

I have a problem with run-time errors coming from an unorthodox use of handles:

  I make use of a triangulation and of an augmented polyhedron_3 object. This augmented polyhedron
is a refinement of the surface represented by the triangulation : as some algorithm goes on, new edges
are added on what used to be the triangular faces. It is important that the halfedges,faces and vertices
on the polyhedron that originate from features of the triangulation should point to the corresponding triangulation
features.  Thus each feature stores a handle of the original triangulation object: a polyhedron vertex stores a handle
to the original triangulation vertex of the same coordinates, a halfedge stores a handle to the triangulation edge or
face on which it lies etc.
 When a feature is refined eg a halfedge is split, these stored handles of triangulation features are copied to
the newly created features. And then segmentation faults appear. Specifically, things go wrong when there is an attempt
to access the handle member object of the new feature outside of the function that created the feature (and copied the
handle object to it).  Any ideas for what could fix this?

thanks

Constantinos




Archive powered by MHonArc 2.6.16.

Top of Page