libupnp

History

Marcelo Roberto Jimenez 28799f26c9 [pupnp-devel] Type mixup on x86_64 causes UPNP_E_OUTOF_MEMORY

Submitted By: Glen Masgai
after an UpnpSendActionAsync() for example, i get UPNP_E_OUTOF_MEMORY
in the callback using 1.4.4 on a x86_64 system. This happens in
http_MakeMessage(), which in some cases get called with wrong types
(int instead of size_t) in combination with format "b" and "Q".
The attached patch should fix this.


git-svn-id: https://pupnp.svn.sourceforge.net/svnroot/pupnp/trunk@166 119443c7-1b9e-41f8-b6fc-b9c35fce742c

2007-04-28 18:42:14 +00:00

doc

Include prebuilt documentation (html,pdf), dropping doc++ dependancy.

2006-07-06 12:37:29 +00:00

inc

typedef modifications for use with Borland Builder

2007-03-03 14:36:58 +00:00

sample

Always retrieve the actual port used by the library. Even if specified the value might be

2006-10-03 10:26:31 +00:00

src

[pupnp-devel] Type mixup on x86_64 causes UPNP_E_OUTOF_MEMORY