While you're at it, this is also probably wrong in ParseOption(opt, arg, req):<br><br>    case 'C':<br>      parseAMF(&req->extras, optarg, &req->edepth);<br>      break;<br><br>optarg will definitely *not* be populated during a HTTP request!<br>
<br><div class="gmail_quote">On Thu, Jul 19, 2012 at 7:44 PM, compn <span dir="ltr"><<a href="mailto:tempn@twmi.rr.com" target="_blank">tempn@twmi.rr.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="im">On Thu, 19 Jul 2012 17:22:03 +0100, Bastien Nocera wrote:<br>
>+    case 'i':<br>
>+      STR2AVAL(req->fullUrl, optarg);<br>
>+      break;<br>
>     case 's':<br>
>       STR2AVAL(req->swfUrl, arg);<br>
>       break;<br>
<br>
</div>i know rtmpdump uses optarg. is there any problem mixing optarg and<br>
arg here ?<br>
<span class="HOEnZb"><font color="#888888"><br>
-compn<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
rtmpdump mailing list<br>
<a href="mailto:rtmpdump@mplayerhq.hu">rtmpdump@mplayerhq.hu</a><br>
<a href="https://lists.mplayerhq.hu/mailman/listinfo/rtmpdump" target="_blank">https://lists.mplayerhq.hu/mailman/listinfo/rtmpdump</a><br>
</div></div></blockquote></div><br>