[prev in list] [next in list] [prev in thread] [next in thread]
List: soot-list
Subject: Re: [Soot-list] Bytecodeoffset Tag probably broken in nightly builds
From: "Steven Arzt" <Steven.Arzt () cased ! de>
Date: 2014-11-21 17:14:29
Message-ID: 004b01d005ae$9bef3d20$d3cdb760$ () 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 Manas,
This happens because the new ASM frontend does not yet support BytecodeOffsetTag. If \
you really need it, you can switch back to coffi using –coffi command-line option. \
Sadly, it is not trivial to get bytecode offsets from ASM without patching the ASM \
class loader. The problem is that ASM never really gives access to such low-level \
information as it operates on a higher level of abstraction.
I have just looked into the problem and was able to extract the bytecode offsets for \
those locations that are ASM labels. The location of a label is not exactly the \
location of the next instruction, though. I have not yet fully understood why there \
is a tiny offset, but it exists. Furthermore, if there is no ASM label (i.e., we are \
in the middle of a basic block and there are no line number annotations), we are out \
of luck anyway. I'm not happy with that, but I don't see a quick way to fix that at \
the moment.
@All: Some ideas?
Best regards,
Steven
Von: soot-list-bounces@CS.McGill.CA [mailto:soot-list-bounces@CS.McGill.CA] Im \
Auftrag von Manas Thakur
Gesendet: Dienstag, 18. November 2014 13:49
An: soot-list@CS.McGill.CA
Betreff: [Soot-list] Bytecodeoffset Tag probably broken in nightly builds
Hi
I have been using the BytecodeOffsetTag in soot-2.5.0. I had updated my Soot version \
from a nightly build last week. When I checked today, the BytecodeOffsetTag was \
always null. I downloaded the latest nightly build again, and found that the problem \
is still there.
Can the developers please check if it's really broken, or there is some new way \
introduced to access the BytecodeOffset of the units?
Regards,
Manas
[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=utf-8"><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-size:10.0pt;}
@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 \
Manas,<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'>This \
happens because the new ASM frontend does not yet support BytecodeOffsetTag. If you \
really need it, you can switch back to coffi using –coffi command-line option. \
Sadly, it is not trivial to get bytecode offsets from ASM without patching the ASM \
class loader. The problem is that ASM never really gives access to such low-level \
information as it operates on a higher level of abstraction.<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'>I have just \
looked into the problem and was able to extract the bytecode offsets for those \
locations that are ASM labels. The location of a label is not exactly the location of \
the next instruction, though. I have not yet fully understood why there is a tiny \
offset, but it exists. Furthermore, if there is no ASM label (i.e., we are in the \
middle of a basic block and there are no line number annotations), we are out of luck \
anyway. I'm not happy with that, but I don't see a quick way to fix that at the \
moment.<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'>@All: Some \
ideas?<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><span lang=EN-US \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div \
style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><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>Manas Thakur<br><b>Gesendet:</b> Dienstag, 18. November 2014 \
13:49<br><b>An:</b> soot-list@CS.McGill.CA<br><b>Betreff:</b> [Soot-list] \
Bytecodeoffset Tag probably broken in nightly \
builds<o:p></o:p></span></p></div></div><p \
class=MsoNormal><o:p> </o:p></p><div><div><div><div><div><p \
class=MsoNormal><span style='color:black'>Hi<o:p></o:p></span></p></div><div><p \
class=MsoNormal><span style='color:black'><o:p> </o:p></span></p></div><div><p \
class=MsoNormal><span style='color:black'>I have been using the BytecodeOffsetTag in \
soot-2.5.0. I had updated my Soot version from a nightly build last week. When I \
checked today, the BytecodeOffsetTag was always null. I downloaded the latest nightly \
build again, and found that the problem is still \
there.<o:p></o:p></span></p></div><div><p class=MsoNormal><span \
style='color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span \
style='color:black'>Can the developers please check if it's really broken, or there \
is some new way introduced to access the BytecodeOffset of the \
units?<o:p></o:p></span></p></div><div><p class=MsoNormal><span \
style='color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span \
style='color:black'>Regards,<o:p></o:p></span></p></div><div><p class=MsoNormal><span \
style='color:black'>Manas<o:p></o:p></span></p></div><div><p class=MsoNormal><span \
style='color:black'><o:p> </o:p></span></p></div></div><p class=MsoNormal><span \
style='color:black'><o:p> </o:p></span></p></div><p class=MsoNormal><span \
style='color:black'><o:p> </o:p></span></p></div><p class=MsoNormal \
style='margin-bottom:12.0pt'><o:p> </o:p></p></div><p \
class=MsoNormal><o:p> </o:p></p></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