search for: parse_err

Displaying 5 results from an estimated 5 matches for "parse_err".

Did you mean: parse_error
2006 Aug 24
1
AMD64 bug
...int(opb,&len); if(len<0)return(OC_BADHEADER); @@ -180,7 +180,8 @@ _tp_readbuffer(opb,tc->vendor, len); tc->vendor[len]='\0'; - _tp_readlsbint(opb,(long *) &tc->comments); + _tp_readlsbint(opb,&tmp); + tc->comments=tmp; if(tc->comments<0)goto parse_err; tc->user_comments=_ogg_calloc(tc->comments,sizeof(*tc->user_comments)); tc->comment_lengths=_ogg_calloc(tc->comments,sizeof(*tc->comment_lengths));
2006 Aug 29
0
Bug#383793: libtheora0: not 64-bit clean
...int(opb,&len); if(len<0)return(OC_BADHEADER); @@ -180,7 +180,8 @@ _tp_readbuffer(opb,tc->vendor, len); tc->vendor[len]='\0'; - _tp_readlsbint(opb,(long *) &tc->comments); + _tp_readlsbint(opb,&tmp); + tc->comments=tmp; if(tc->comments<0)goto parse_err; tc->user_comments=_ogg_calloc(tc->comments,sizeof(*tc->user_comments)); tc->comment_lengths=_ogg_calloc(tc->comments,sizeof(*tc->comment_lengths));
2013 Sep 13
10
[PATCH RFC 0/8] xen/arm: initial cubieboard2 support.
See http://www.gossamer-threads.com/lists/xen/devel/297170 for some information on how to get this going. I''ve rebased and addressed the review comments. As before several of the patches are not to be applied because they can be done better using infrastructure from Julien''s "Allow Xen to boot with a raw Device Tree" patch. They are included for completeness. With
2013 Sep 20
20
[PATCH v3 0/7] support for cubieboard2 / sunxi processors
See http://www.gossamer-threads.com/lists/xen/devel/297170 for some information on how to get this going. I''ve rebased and addressed the review comments. With this rebase I''ve picked up some patches from Julien which were required to do things properly, so the gic v7 and device blacklisting patches have been changed to use the proper mechanisms. Previously I was able to boot
2013 Jul 22
69
[xen-unstable] Commit 2ca9fbd739b8a72b16dd790d0fff7b75f5488fb8 AMD IOMMU: allocate IRTE entries instead of using a static mapping, makes dom0 boot process stall several times.
Hi Jan, After commit 2ca9fbd739b8a72b16dd790d0fff7b75f5488fb8 AMD IOMMU: allocate IRTE entries instead of using a static mapping, booting dom0 stalls several times. Sometimes this results in RCU stall warnings from the dom0 kernel, hitting the "any" key, on normal or serial console, makes the boot continue for a while but it stalls several times. (It also stalls on shutdown BTW) I have