[Soot-list] other inputs except java and class files

Zeinab Lashkaripour lashkaripour at yahoo.com
Fri Jan 25 14:47:58 EST 2013


ThanksMarc-Andre,
Considering what you said before I think that maybe converting to java then trying to use Soot is better. 

Do you agree?




________________________________
 From: Marc-Andre Laverdiere-Papineau <marc-andre.laverdiere-papineau at polymtl.ca>
To: "soot-list at sable.mcgill.ca" <soot-list at sable.mcgill.ca> 
Sent: Friday, January 25, 2013 11:05 PM
Subject: Re: [Soot-list] other inputs except java and class files
 
Every database engine has a bunch of built-in functions that you have to 
take in consideration...

Marc-André Laverdière-Papineau
Doctorant - PhD Candidate

On 13-01-25 11:21 AM, Zeinab Lashkaripour wrote:
> Thanks Marc-Andre,
> Your reply was nice and sufficient but I have a question:
> What did you mean by library calls?
>
> ------------------------------------------------------------------------
> *From:* Marc-Andre Laverdiere-Papineau
> <marc-andre.laverdiere-papineau at polymtl.ca>
> *To:* soot-list at sable.mcgill.ca
> *Sent:* Friday, January 25, 2013 6:41 PM
> *Subject:* Re: [Soot-list] other inputs except java and class files
>
> Hello,
>
> Soot is really meant to handle Java bytecode. In other words, it can
> handle things that have Java semantics.
>
> So if your stored procedures are in a language that has a subset of the
> Java semantics, then you can express them in Java in a
> behavior-preserving fashion.
>
> I don't really know how they are implemented, but I know that most in
> variants of SQL. That language is minimalistic and should be
> translatable easily. However, you will need to model the library calls -
> so that will be a lot of work.
>
> Even if you do that, there are the side-effects - what happens if you
> change the tables and the like?
>
> So, in other words, you need to set a limit of how much you're willing
> to handle.
>
> You may also want to consider translating directly to Jimple. That way,
> you save a processing step, but it means you're bound to soot forever
> (and maybe your requirements go in the other direction).
>
> Marc-André Laverdière-Papineau
> Doctorant - PhD Candidate
>
> On 13-01-25 09:59 AM, Zeinab Lashkaripour wrote:
>  > Hello,
>  > I wanted to know if I need to do data flow analysis on some Stored
>  > Procedures of a database which way do you think would be better to
> choose?
>  > 1. Convert them with a parser to java code and use Soot?
>  > 2. Do the analysis by myself?
>  >
>  > Thanks in advance,
>  >
>  >
>  >
>  > _______________________________________________
>  > Soot-list mailing list
>  > Soot-list at sable.mcgill.ca <mailto:Soot-list at sable.mcgill.ca>
>  > http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
>  >
> _______________________________________________
> Soot-list mailing list
> Soot-list at sable.mcgill.ca <mailto:Soot-list at sable.mcgill.ca>
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
>
>
_______________________________________________
Soot-list mailing list
Soot-list at sable.mcgill.ca
http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.cs.mcgill.ca/pipermail/soot-list/attachments/20130125/36e47517/attachment.html 


More information about the Soot-list mailing list