diff options
| author |  Berthold Stoeger <bstoeger@mail.tuwien.ac.at> | 2019-07-27 22:30:09 +0200 |
|---|---|---|
| committer |  Dirk Hohndel <dirk@hohndel.org> | 2019-07-27 14:57:31 -0700 |
| commit | b0f1b258064bcbeb9cfc70dd4346dde5a90546ea (patch) | |
| tree | db874fcd28b9e2b0e021bf964d14bf4110a4e6ec /core/file.c | |
| parent | a0cd89f850d727f161eba19e0ee4b19e5aaf8f57 (diff) | |
| download | subsurface-b0f1b258064bcbeb9cfc70dd4346dde5a90546ea.tar.gz | |
Crash fix: prevent crash in MapLocationModel::reload
Commit 0c387549164d7eec3ea6647c54ada2fba7f8d5e6 introduced a
bug in MapLocationModel::reload() by setting an entry in the
name-to-location map before the location was initialized.
Move the setting of the map entry back where it was before:
after the assignment of the location variable.
Moreover, define the location variable directly on allocation
of the location to avoid thus bugs in the future.
Why did we not get a "might be used unitialized" warning
anyway?
Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>
Diffstat (limited to 'core/file.c')
0 files changed, 0 insertions, 0 deletions