DOLFIN

Empty EpetraMatrix is error prone

Bug #822149 reported by Johan Hake on 2011-08-07

6

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	DOLFIN	Fix Released	Medium	Unassigned	DOLFIN 1.0-beta2

Bug Description

When an Empty EpetraMatrix is initialized the underlying EpetraFECrsMatrix does not get initialized.
This results in an assert in the EpetraMatrix::operator= method when this method is called from an empty EpetraMatrix, from rev 6068 and older. In rev 6073.1.1 the operator= bug is fixed using the copy constructor of the EpetraFECrsMatrix.

See original description

Revision history for this message

Johan Hake (johan-hake) wrote on 2011-08-07:

#1

A minimal example that reveals the bug for rev earlier than -rev 6069 Edit (219 bytes, text/x-python)

description:

updated

Garth Wells (garth-wells) on 2011-08-24

Changed in dolfin:
status:	New → Fix Committed
milestone:	none → 1.0-rc1

Anders Logg (logg) on 2011-09-20

Changed in dolfin:
milestone:	1.0-rc1 → 1.0-beta2

Garth Wells (garth-wells) on 2011-10-05

Changed in dolfin:
importance:	Undecided → Medium

Garth Wells (garth-wells) on 2011-10-26

Changed in dolfin:
status:	Fix Committed → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

A minimal example that reveals the bug for rev earlier than -rev 6069 Edit

Add attachment

Remote bug watches

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