You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Dr. Zhu, I'm using your Recoder tool to repair some new bugs and it turns out to be really so powerful! But I observed that on some cases it may fail in post processing phase and I wonder you can help confirm that. In your testone.py script which is the core component of Recoder,
tries to judge whether there's a throw statement in lines[0]. This lines is directly from aftercode which is part of the context. But for some special cases where the buggy method is too short (e.g. only one line, like int sum(int a, int b) { return a + b;}), the aftercode is actually empty and so is lines. Therefore lines[0] will trigger an Index Error: list out of range error. I think fixing this issue may help Recoder to fix more bugs. Thank you for taking a look.
The text was updated successfully, but these errors were encountered:
Hi Dr. Zhu, I'm using your Recoder tool to repair some new bugs and it turns out to be really so powerful! But I observed that on some cases it may fail in post processing phase and I wonder you can help confirm that. In your
testone.py
script which is the core component of Recoder,Recoder/testone.py
Line 441 in 83de143
lines[0]
. Thislines
is directly fromaftercode
which is part of the context. But for some special cases where the buggy method is too short (e.g. only one line, like int sum(int a, int b) { return a + b;}), theaftercode
is actually empty and so islines
. Thereforelines[0]
will trigger anIndex Error: list out of range
error. I think fixing this issue may help Recoder to fix more bugs. Thank you for taking a look.The text was updated successfully, but these errors were encountered: