Don't attempt to use a BASE_CUSTOM field's 'strings' field as a
value_string: it's not, it's a pointer to a function.

svn path=/trunk/; revision=35115
This commit is contained in:
Jeff Morriss 2010-12-03 22:59:16 +00:00
parent 5a7b4defa3
commit 39f6874d13
1 changed files with 11 additions and 0 deletions

View File

@ -230,6 +230,17 @@ mk_fvalue_from_val_string(header_field_info *hfinfo, char *s)
hfinfo->abbrev);
return NULL;
}
else if (hfinfo->display & BASE_CUSTOM) {
/* If a user wants to match against a custom string, we would
* somehow have to have the integer value here to pass it in
* to the custom-display function. But we don't have an
* integer, we have the string they're trying to match.
* -><-
*/
dfilter_fail("\"%s\" cannot accept [custom] strings as values.",
hfinfo->abbrev);
return NULL;
}
else {
const value_string *vals = hfinfo->strings;
if (hfinfo->display & BASE_EXT_STRING)