Re: [Pyobjc-dev] PyObjC trunk 64-bit bridgesupport patch

[Ronald O. <ron...@ma...>]

Thanks for the patch, I'll apply both this one and the bridgesupport  
patch you posted earlier.

I'd prefer to completely fail on invalid metadata files, but need to  
fix pyobjc's metadata tools before I do that.  The pyobjc-metadata  
project contains tools for working with metadata files, but sadly  
enough those are broken at the moment. One of the tools in there is a  
script that verifies the contents of a brigesupport file and gives  
more useful warnings and/or errors.

Ronald

On 24 Apr, 2009, at 15:00, James R Eagan wrote:

> And here's the follow-up patch I referred to yesterday.  This one  
> modifies parsexml.m to avoid a segfault on malformed typestrings (at  
> least malformed such that the type spec is missing).  It also  
> modifies obj/_bridgesupport.py to output a more user-friendly warning.
>
> I'm not sure this is necessarily the right approach ... perhaps it  
> would be better to simply ignore invalid signatures instead of the  
> entire module.  But at least now the user will see a meaningful  
> error rather than a cryptic segfault when loading frameworks with  
> faulty bridgesupport metadata.
>
> Cheers!
> James
>
> <bridgesupport-bogus-data-nocrash.patch>
>
> PS: Apologies about the previous email.  I have no idea why that  
> duplicate went out.  Pixie dust in the  
> keyboard 
> ?------------------------------------------------------------------------------
> Crystal Reports &#45; New Free Runtime and 30 Day Trial
> Check out the new simplified licensign option that enables unlimited
> royalty&#45;free distribution of the report engine for externally  
> facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects_______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev