8000 Fix missing files in meson.build by CyrilBrulebois · Pull Request #207 · frida/frida-tools · GitHub
[go: up one dir, main page]

Skip to content

Fix missing files in meson.build - #207

Closed
CyrilBrulebois wants to merge 2 commits into
frida:mainfrom
CyrilBrulebois:main
Closed

CyrilBrulebois wants to merge 2 commits into
frida:mainfrom
CyrilBrulebois:main

Conversation

@CyrilBrulebois
Copy link
Copy Markdown
Contributor

These two commits fix a specific regression in 17.15.0 (due to the introduction of repl_inspect.py) and a more general disparity between the contents of the Git repository and the set of files deployed by the build system.

Traceback for the specific regression, starting with 17.15.0:

$ frida --help
Traceback (most recent call last):
  File "/usr/bin/frida", line 6, in <module>
    import frida_tools.repl
  File "/usr/lib/python3/dist-packages/frida_tools/repl.py", line 32, in <module>
    from frida_tools import _repl_magic, repl_inspect
ImportError: cannot import name 'repl_inspect' from 'frida_tools' (/usr/lib/python3/dist-packages/frida_tools/__init__.py)

Commit f7384b5 introduces a dependency
on a new file (repl_inspect.py) without adding it to meson.build; this
means that `make install` doesn't deploy this file, leading to trivial
import issues down the line.

Spotted with trivial commands like `frida -f /usr/bin/df` initially, but
even `frida --help` fails:

    $ frida --help
    Traceback (most recent call last):
      File "/usr/bin/frida", line 6, in <module>
        import frida_tools.repl
      File "/usr/lib/python3/dist-packages/frida_tools/repl.py", line 32, in <module>
        from frida_tools import _repl_magic, repl_inspect
    ImportError: cannot import name 'repl_inspect' from 'frida_tools' (/usr/lib/python3/dist-packages/frida_tools/__init__.py)

Regression first published with 17.15.0, while 17.14.1 was still fine.
While investigating the repl_inspect.py regression (addressed in the
previous commit), it was spotted that other files are missing from the
sources list. The consequences have not been investigated specifically
but it seems prudent to ship all those files.
@oleavr
oleavr commented Nov 5, 2026 •
Copy link
Copy Markdown
Member

Thanks! Landed as 33637cc and f881de0 (with subject lines tweaked to match the project's commit style).

@oleavr oleavr closed this Nov 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

0