Displaying 2 results from an estimated 2 matches for "field_name_".
Did you mean:
field_name
2012 May 07
3
[PATCH] Add missing functions to VorbisComment class + a few other things
...ve this on my system.
Lastly, the reason I tried to compile with debug was some invalid read sizes reported by valgrind when creating a VorbisComment::Entry. The invalid read is reported in set_field_name() at line 653 (src/libFLAC++/metadata.cpp), where strlen() is used on the newly created char *field_name_. I could not see anything wrong with the code though, and strangely enough just calling printf on the field_name_ 1 line before the strlen() removes all valgrind errors. So I'm not sure what's going on, but it's probably a bug in valgrind, maybe somebody on this list knows?
Bas Timmer...
2012 May 08
0
[PATCH] Add missing functions to VorbisComment class + a few other things
...; Lastly, the reason I tried to compile with debug was some invalid read
> sizes reported by valgrind when creating a VorbisComment::Entry. The
> invalid read is reported in set_field_name() at line 653 (
> src/libFLAC++/metadata.cpp), where strlen() is used on the newly created
> char *field_name_. I could not see anything wrong with the code though,
> and strangely enough just calling printf on the field_name_ 1 line before
> the strlen() removes all valgrind errors. So I'm not sure what's going on,
> but it's probably a bug in valgrind, maybe somebody on this list know...