Opened 15 years ago
Last modified 14 years ago
#19 closed task
memory corruption issues WHIZARD 1 — at Version 3
| Reported by: | Christian Speckner | Owned by: | ALL |
|---|---|---|---|
| Priority: | P3 | Milestone: | |
| Component: | core | Version: | 1.93 |
| Severity: | normal | Keywords: | memory corruption |
| Cc: |
Description (last modified by )
Analyse corruption of WHIZARD 1 structures using compiler options and the valgrind.
Change History (3)
comment:1 Changed 15 years ago by
comment:2 Changed 15 years ago by
| Summary: | memory leak analysis of WHIZARD 1 → memory corruption investigation for WHIZARD 1 |
|---|
comment:3 Changed 15 years ago by
| Description: | modified (diff) |
|---|---|
| Keywords: | corruption added; leak analysis removed |
| Reporter: | changed from Juergen Reuter to Christian Speckner |
| Summary: | memory corruption investigation for WHIZARD 1 → memory corruption issues WHIZARD 1 |
Note: See
TracTickets for help on using
tickets.
You might want to look at the patches that I checked into my 1.93_fix_corruption branch. These address a couple of memory corruption issues that can be found via compiler switches (or valgrind). However, they are just workarounds which don't really fix the issues.