Stack blowout in _w95_dump_dke

[by way of Troy Rollo <troy at corvu.com.au>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

_w95_dump_dke has code in it that processes sibling keys in the registry
recursively. This results in a stack blowout for large registries (in my case
in the Software\CLASSES key).

It's trivial to stop the stack blowing out by changing this not to be
recursive, but processing siblings recursively is such an unusual thing to do
that I suspect it must have been done for a reason. Attached is the way I've
"fixed" it, but this causes the keys to be output in the opposite order to
the way they are output with the CVS code.

Is there a reason this needs to be done in the order the CVS code is doing
 it?


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA8bbd2IoBoXB5Q0kRAoJEAJ9IbtBVxkly+8t8LPL2ZmD/RVwq6wCdHG2t
QxlBYcbU/VVdeXLx0QVgQlo=
=ZSKw
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: diffs
Type: text/x-diff
Size: 1668 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-devel/attachments/20040712/94b8381b/diffs.bin