Opened 13 years ago
Closed 13 years ago
#426 closed defect (fixed)
WHIZARD unit test seg faults
| Reported by: | Juergen Reuter | Owned by: | kilian |
|---|---|---|---|
| Priority: | P3 | Milestone: | v2.0.6 |
| Component: | core | Version: | 2.0.5 |
| Severity: | normal | Keywords: | seg fault |
| Cc: |
Description
Doing
whizard --check expressions
results in a seg fault.
Change History (3)
comment:1 Changed 13 years ago by
| Keywords: | seg fault added |
|---|
comment:2 Changed 13 years ago by
Note: See
TracTickets for help on using
tickets.
The seg fault is caused by the
call var_list_writebecause after the last component of the var list gets unassociated, it for some reason believes to have to write something else which is, however, not initialised. When inserting a var_list_write statement into the call var_list_set_observables_unary inside eval_node_set_observables does not result in a seg fault. This is triggered by the flag write_next, which is set by the associated statement of var_list%next.