debugging when JIT a compiled function is derived from string exec

[chaoming0625]

---

Feature request

Currently, Numba does not have a good mode to debug a jitted function without source code. For example, when I have the following compiled code:

import numba

code = '''
def f(a, b):
  a[0] = b
'''

scope = {}
exec(compile(code, '', 'exec'), scope)
f = numba.njit(scope['f'])

After I jit the compiled function and run it,

f(1, 2)

the code has an error, and the numba reports:

numba.core.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend)
No implementation of function Function(<built-in function setitem>) found for signature:
 
 >>> setitem(int64, Literal[int](0), int64)
 
There are 16 candidate implementations:
  - Of which 16 did not match due to:
  Overload of function 'setitem': File: <numerous>: Line N/A.
    With argument(s): '(int64, int64, int64)':
   No match.

During: typing of staticsetitem at  (3)

File "D:\codes\Projects\BrainPy\develop\test\numba", line 3:
<source missing, REPL/exec in use?>

Numba cannot report where the error is raised, because <source missing, REPL/exec in use?>

When the compiled function is a large program, such debugging is very very difficult!!!

Can we support the error debugging for such compiled function in a more nice way? For example, when I jit the compiled function, I can provide the souce code:

f = numba.njit(scope['f'], source_code=code)

Thank you very much!

[gmarkall]

This is an interesting idea - we'll discuss it at the triage meeting today.

[chaoming0625]

@gmarkall Thank you very much.

Currently, I intensely use this kind of way to jit compiled functions. After I recursively jit nested compiled functions, debugging is very very difficult!

[stuartarchibald]

Thanks for the request. Have updated the title to reflect the need to link string source to debug output. Another option might be to patch the code objects and inject into linecache.

[github-actions]

This issue is marked as stale as it has had no activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with any updates and confirm that this issue still needs to be addressed.

[gmarkall]

I've removed needtriage so this won't go stale again.