[prev in list] [next in list] [prev in thread] [next in thread]
List: soot-list
Subject: Re: [Soot-list] Suppress Soot warning from log
From: "Steven Arzt" <Steven.Arzt () cased ! de>
Date: 2015-06-08 9:45:28
Message-ID: 008101d0a1cf$da6af810$8f40e830$ () cased ! de
[Download RAW message or body]
This is a multipart message in MIME format.
[Attachment #2 (multipart/alternative)]
This is a multipart message in MIME format.
Hi Zheran,
Some components of Soot do not use the normal logging mechanism. There is
some ongoing work in changing the logging mechanism, e.g., see this pull
request: https://github.com/Sable/soot/pull/401. FlowDroid should already
use slf4j for all logging. If you find cases in which soot-infoflow or
soot-infoflow-android directly print out to the command-line instead of
going through slf4j, please feel free to open up a pull request to fix that
issue.
Best regards,
Steven
Von: soot-list-bounces@CS.McGill.CA [mailto:soot-list-bounces@CS.McGill.CA]
Im Auftrag von R.F.
Gesendet: Mittwoch, 3. Juni 2015 13:10
An: Bodden, Eric
Cc: soot-list@cs.mcgill.ca
Betreff: Re: [Soot-list] Suppress Soot warning from log
Hi, Eric,
Thanks for your answer. However, now every time I initialize Soot, I added
`G.v().out = new PrintStream(new File("/dev/null"));`, but some messages are
still outputted in the log. Did I do something wrong or miss something?
I also use soot-infoflow-android in my work, and I notice that classes such
as AnalyzeJimpleClass of soot-infoflow-android output directly via
System.out.
Moreover, after I set G.v().out, is error output redirected as well? I found
that I cannot access or modify G.v().err.
Thank you.
Best Regards,
Zheran Fang
On Wed, May 27, 2015 at 2:41 PM, Bodden, Eric
<eric.bodden@sit.fraunhofer.de> wrote:
Hi.
You can overwrite the output stream stored in G.v().out with one that prints
nothing.
Cheers,
Eric
> On 26.05.2015, at 18:15, R.F. <rayfang1991@hotmail.com> wrote:
>
> Hi,
>
> When running Soot, it will print messages like "Warning: SOMECLASS is a
phantom class", "[Spark] ******" , etc, in the output log.
>
> Is there any option to prevent Soot from printing anything, including
infos or warnings in the output log?
>
> Thanks.
>
>
> Best Regards,
> R. F.
> _______________________________________________
> Soot-list mailing list
> Soot-list@CS.McGill.CA
> https://mailman.CS.McGill.CA/mailman/listinfo/soot-list
--
Prof. Eric Bodden, Ph.D., http://sse.ec-spride.de/ http://bodden.de/
Head of Secure Software Engineering at Fraunhofer SIT, TU Darmstadt and EC
SPRIDE
Tel: +49 6151 16-75422 <tel:%2B49%206151%2016-75422> Fax: +49 6151
869-127 <tel:%2B49%206151%20869-127>
Room B5.11, Fraunhofer SIT, Rheinstraße 75, 64295 Darmstadt
[Attachment #5 (text/html)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type \
content="text/html; charset=iso-8859-1"><meta name=Generator content="Microsoft Word \
14 (filtered medium)"><style><!-- /* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=DE link=blue vlink=purple><div \
class=WordSection1><p class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi \
Zheran,<o:p></o:p></span></p><p class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p \
class=MsoNormal><span lang=EN-US \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Some \
components of Soot do not use the normal logging mechanism. There is some ongoing \
work in changing the logging mechanism, e.g., see this pull request: <a \
href="https://github.com/Sable/soot/pull/401">https://github.com/Sable/soot/pull/401</a>. \
FlowDroid should already use slf4j for all logging. If you find cases in which \
soot-infoflow or soot-infoflow-android directly print out to the command-line instead \
of going through slf4j, please feel free to open up a pull request to fix that \
issue.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p \
class=MsoNormal><span lang=EN-US \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Best \
regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> \
Steven<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p \
class=MsoNormal><b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Von:</span></b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> \
soot-list-bounces@CS.McGill.CA [mailto:soot-list-bounces@CS.McGill.CA] <b>Im Auftrag \
von </b>R.F.<br><b>Gesendet:</b> Mittwoch, 3. Juni 2015 13:10<br><b>An:</b> Bodden, \
Eric<br><b>Cc:</b> soot-list@cs.mcgill.ca<br><b>Betreff:</b> Re: [Soot-list] Suppress \
Soot warning from log<o:p></o:p></span></p><p \
class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Hi, \
Eric,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p \
class=MsoNormal>Thanks for your answer. However, now every time I initialize Soot, I \
added `G.v().out = new PrintStream(new File("/dev/null"));`, but some \
messages are still outputted in the log. Did I do something wrong or miss \
something?<o:p></o:p></p></div><div><p \
class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I also use \
soot-infoflow-android in my work, and I notice that classes such as \
AnalyzeJimpleClass of soot-infoflow-android output directly via \
System.out.<o:p></o:p></p></div><div><p \
class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Moreover, after I \
set G.v().out, is error output redirected as well? I found that I cannot access or \
modify G.v().err.<o:p></o:p></p></div><div><p \
class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thank \
you.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p \
class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Best \
Regards,<o:p></o:p></p></div><div><p class=MsoNormal>Zheran \
Fang<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p><div><p \
class=MsoNormal>On Wed, May 27, 2015 at 2:41 PM, Bodden, Eric <<a \
href="mailto:eric.bodden@sit.fraunhofer.de" \
target="_blank">eric.bodden@sit.fraunhofer.de</a>> wrote:<o:p></o:p></p><p \
class=MsoNormal>Hi.<br><br>You can overwrite the output stream stored in G.v().out \
with one that prints nothing.<br><br>Cheers,<br>Eric<o:p></o:p></p><div><div><p \
class=MsoNormal><br>> On 26.05.2015, at 18:15, R.F. <<a \
href="mailto:rayfang1991@hotmail.com">rayfang1991@hotmail.com</a>> \
wrote:<br>><br>> Hi,<br>><br>> When running Soot, it will print messages \
like "Warning: SOMECLASS is a phantom class", "[Spark] ******" , \
etc, in the output log.<br>><br>> Is there any option to prevent Soot from \
printing anything, including infos or warnings in the output log?<br>><br>> \
Thanks.<br>><br>><br>> Best Regards,<br>> R. \
F.<o:p></o:p></p></div></div><p class=MsoNormal style='margin-bottom:12.0pt'>> \
_______________________________________________<br>> Soot-list mailing \
list<br>> <a href="mailto:Soot-list@CS.McGill.CA">Soot-list@CS.McGill.CA</a><br>> \
<a href="https://mailman.CS.McGill.CA/mailman/listinfo/soot-list" \
target="_blank">https://mailman.CS.McGill.CA/mailman/listinfo/soot-list</a><br><br>--<br>Prof. \
Eric Bodden, Ph.D., <a href="http://sse.ec-spride.de/" \
target="_blank">http://sse.ec-spride.de/</a> <a href="http://bodden.de/" \
target="_blank">http://bodden.de/</a><br>Head of Secure Software Engineering at \
Fraunhofer SIT, TU Darmstadt and EC SPRIDE<br>Tel: <a \
href="tel:%2B49%206151%2016-75422">+49 6151 16-75422</a> Fax: <a \
href="tel:%2B49%206151%20869-127">+49 6151 869-127</a><br>Room B5.11, Fraunhofer SIT, \
Rheinstraße 75, 64295 Darmstadt<o:p></o:p></p></div><p \
class=MsoNormal><o:p> </o:p></p></div></div></body></html>
_______________________________________________
Soot-list mailing list
Soot-list@CS.McGill.CA
https://mailman.CS.McGill.CA/mailman/listinfo/soot-list
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic