Ryan Lortie f76e4ef683 typelib compiler: properly initialise memory
The typelib compiler was writing uninitialised memory to the output file.

There were two sources of this uninitialised memory: the hash writer included
some uninitialised memory in its output, and the bytes added after the hash
output for padding were also not being initialised.

Fix this by passing the padded size to the hash code writer function and
having that function initialise the entire memory region to zero before
writing.

https://bugzilla.gnome.org/show_bug.cgi?id=721177
2013-12-30 22:31:53 -05:00
2012-10-16 10:58:08 -04:00
2013-10-10 16:48:51 -04:00
2012-10-16 10:58:08 -04:00
2013-10-10 16:48:51 -04:00
2013-10-10 16:48:51 -04:00
2013-10-10 16:48:51 -04:00
2013-10-10 16:48:51 -04:00
2013-10-10 16:48:51 -04:00
2013-10-10 16:48:51 -04:00
2013-10-10 16:48:51 -04:00
2013-10-10 16:48:51 -04:00
2013-10-10 16:48:51 -04:00
2012-02-03 13:42:56 -05:00
2013-11-29 18:45:31 +00:00
2013-10-10 16:48:51 -04:00
2012-02-03 13:42:56 -05:00
2012-02-03 13:42:56 -05:00
2013-10-10 16:48:51 -04:00
2013-10-10 16:48:51 -04:00
2013-10-10 16:48:51 -04:00
2013-10-10 16:48:51 -04:00
2013-10-10 16:48:51 -04:00
2012-10-16 10:58:08 -04:00
Description
Low-level core library that forms the basis for projects such as GTK+ and GNOME.
124 MiB
Languages
C 95.3%
Python 2.3%
Meson 1.3%
Objective-C 0.3%
Shell 0.2%
Other 0.5%