Opened 9 years ago

Closed 8 years ago

#704 closed discussion (wontfix)

throw rather than abort in assertions

Reported by: Peter Owned by: Peter
Priority: major Milestone:
Component: utility Version: 0.8.1
Keywords: Cc:

Description

I had a mysterious bug/crash that after relinking against a debug libyat with assertions activated turned out to be an out of range in Matrix::operator(). So I needed to go through all matrices, which was tedious and tiresome. I realized it would've been easier if assert had thrown an exception instead, so one could frame down the buggy code.

We're already doing this in header files with macro YAT_ASSERT, and I think I'd prefer to have all those replaced.

Change History (2)

comment:1 Changed 8 years ago by Peter

Milestone: yat 0.x+yat 0.11
Owner: changed from Jari Häkkinen to Peter

comment:2 Changed 8 years ago by Peter

Milestone: yat 0.11
Resolution: wontfix
Status: newclosed

note to myself: use gdb to trace down the bug

Note: See TracTickets for help on using tickets.