summaryrefslogtreecommitdiff
path: root/keywords.c
diff options
context:
space:
mode:
authorSimon Tatham <anakin@pobox.com>2017-05-14 08:11:06 +0100
committerSimon Tatham <anakin@pobox.com>2017-05-14 08:44:15 +0100
commitc00d1c3b6003dbbb72439de0ebdb4a93c8763f65 (patch)
tree548ad96cb72398c69625ec670beeb90c0566a15d /keywords.c
parent94831068fb5573b1ebdb9def9c2ad09f0694d45c (diff)
downloadhalibut-c00d1c3b6003dbbb72439de0ebdb4a93c8763f65.zip
halibut-c00d1c3b6003dbbb72439de0ebdb4a93c8763f65.tar.gz
halibut-c00d1c3b6003dbbb72439de0ebdb4a93c8763f65.tar.bz2
halibut-c00d1c3b6003dbbb72439de0ebdb4a93c8763f65.tar.xz
Add missing initialisations in the 'word' structure.
The 'breaks' and 'aux' fields were filled in rather inconsistently at various places where a word is created - especially the outlying ones that manufacture pieces of document during internal processing of contents, index, bibliography, cross-references etc rather than directly from the input file. This has never led to any user-visible behaviour change that I've noticed, but it made a lot of annoying noise in the valgrind output, which got in my way last week when I was trying to debug the CHM generation.
Diffstat (limited to 'keywords.c')
-rw-r--r--keywords.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/keywords.c b/keywords.c
index 14aa6bd..c117346 100644
--- a/keywords.c
+++ b/keywords.c
@@ -139,6 +139,8 @@ void subst_keywords(paragraph *source, keywordlist *kl) {
close->alt = NULL;
close->type = word_XrefEnd;
close->fpos = ptr->fpos;
+ close->breaks = FALSE;
+ close->aux = 0;
close->next = ptr->next;
ptr->next = subst;