<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Hi Laura. A great idea and thank you! I had a hand in writing the original version of said script but can’t recall why those tokens were included as reserved. However, according to git-blame there isn’t much left of Achille’s ship. One option would be to remove those words from the script and run it and see what happens? My guess is that they “handled” some annoying failure. <br><br><div dir="ltr" id="AppleMailSignature">Sent from my iPad</div><div dir="ltr"><br>On Oct 14, 2019, at 7:17 AM, Mann, Laura L [US] (MS) <<a href="mailto:laura.mann@ngc.com">laura.mann@ngc.com</a>> wrote:<br><br></div><div dir="ltr">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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]-->
<div class="WordSection1">
<p class="MsoNormal">We’re looking at updating the syscalls2 plugin to work with 64-bit linux. There’s a list of “reserved” words in the syscall_parser.py file that is used to determine what system call argument names need to be renamed. I understand why
“new” and “int” are in the list – they are C/C++ reserved words. But why are “cpu” and “data” in the list? Under what definition of “reserved” words do they fall?<o:p></o:p></p>
<p class="MsoNormal">There are some new system call argument names in the 64-bit system calls, and I want to ensure any which are “reserved” (under whatever definition is being used) are so indicated.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">Laura L. Mann<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div><div dir="ltr"><span>_______________________________________________</span><br><span>panda-users mailing list</span><br><span><a href="mailto:panda-users@mit.edu">panda-users@mit.edu</a></span><br><span><a href="http://mailman.mit.edu/mailman/listinfo/panda-users">http://mailman.mit.edu/mailman/listinfo/panda-users</a></span><br></div></body></html>