Tony Arkles wrote:
>
> Taras Glek wrote:
>
>
>    
>> [EMAIL PROTECTED] wrote:
>>      
>>> Hi,
>>>
>>> I'm trying to use Dehydra to identify uncaught exceptions.  So far,
>>> I've been able to identify:
>>>
>>> * which functions will throw an exception (they will make a call to
>>> __cxa_allocate_exception and __cxa_throw)
>>> * which functions will catch an exception (they will make a call to
>>> __cxa_begin_catch and __cxa_end_catch)
>>>
>>> But I haven't yet been able to identify which sections in a function
>>> are included in a try{} block.  Is there some obvious way to do this
>>> with Dehydra that I've just missed, or is this something that isn't
>>> implemented?
>>>
>>>        
>> You could do this with Treehydra, but it's not supported in Dehydra. I
>> don't think the Dehydra model deals well with function bodies. If
>> someone can come up with a clean way of presenting scopes, etc, that'd
>> be cool.
>>      
>
> Is there any documentation available for Treehydra?  I've got it
> compiled and running, but things are going a bit slow, since I'm
> basically learning how to use it based on the outparams.js sample
> script.
>    
yeah sorry. I'm not quite sure where to start on the docs. Luckily your 
needs are simple(outparams.js is way fancier than what you need).

Take a look at test/finalizers.js
Basically gcc docs + existing js code is only way to get this. I think 
the finalizers stuff will be enough for you.

https://bugzilla.mozilla.org/show_bug.cgi?id=436342 sql.js from there is 
another "simple" enough example.
> If docs aren't available, I suppose it'll probably be beneficial to
> learn more about the gcc parse tree anyway :)
>    
Feel free to make notes as you are learning on the treehydra mdc wiki, 
i'll flesh it out. It's helpful to have a newbie perspective.
Also come by the irc channel, we are happy to do some interactive help.
> Cheers, thanks again for the hard work, this set of tools is super cool
> Tony
>    

Thanks,
Taras
>
>
>    

_______________________________________________
Dev-static-analysis mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-static-analysis

Reply via email to