Package Details: python-frida-tools 12.4.2-1

Git Clone URL: (read-only, click to copy)
Package Base: python-frida-tools
Description: CLI tools for Frida. Python 3 version from PyPi.
Upstream URL:
Licenses: wxWindows Library License, Version 3.1
Conflicts: python2-frida-tools
Submitter: algebro
Maintainer: kriskras99
Last Packager: kriskras99
Votes: 11
Popularity: 1.64
First Submitted: 2018-11-13 18:00 (UTC)
Last Updated: 2024-05-21 21:31 (UTC)

Latest Comments

kriskras99 commented on 2024-05-26 21:40 (UTC)

@Viterzgir I've also had that happen in the past, but I can't reproduce it anymore. The build system downloads an SDK (which I'm trying to change: So maybe it was fixed in a later SDK version. Please try reinstalling it.

Viterzgir commented on 2024-05-22 00:11 (UTC)

Can't build also same error in python-frida package [214/283] Linking target subprojects/frida-core/lib/agent/ ../subprojects/frida-gum/bindings/gumjs/gumv8kernel.cpp:20:6: warning: type ‘GumMemoryValueType’ violates the C++ One Definition Rule [-Wodr] 20 | enum GumMemoryValueType | ^ ../subprojects/frida-gum/bindings/gumjs/gumv8memory.cpp:27:6: note: an enum with different value name is defined in another translation unit 27 | enum GumMemoryValueType | ^ ../subprojects/frida-gum/bindings/gumjs/gumv8kernel.cpp:22:3: note: name ‘GUM_MEMORY_VALUE_S8’ differs from name ‘GUM_MEMORY_VALUE_POINTER’ defined in another translation unit 22 | GUM_MEMORY_VALUE_S8, | ^ ../subprojects/frida-gum/bindings/gumjs/gumv8memory.cpp:29:3: note: mismatching definition 29 | GUM_MEMORY_VALUE_POINTER, | ^ [215/283] Generating subprojects/frida-core/lib/agent/frida-agent-modulated with a custom command FAILED: subprojects/frida-core/lib/agent/ /usr/bin/python3 ../subprojects/frida-core/tools/ --endian little --nm '>>>' /usr/bin/nm '<<<' --readelf '>>>' /usr/bin/readelf '<<<' --otool '>>>' '' '<<<' --output subprojects/frida-core/lib/agent/ subprojects/frida-core/lib/agent/ --move constructor frida_init_memory first --move destructor frida_deinit_memory first

kriskras99 commented on 2023-01-01 18:17 (UTC)

@aulonsal I got 404s the last time I used it. But it seems to be working again. With the next update I will switch back to using it.

aulonsal commented on 2023-01-01 15:55 (UTC) (edited on 2023-01-01 15:55 (UTC) by aulonsal)

Why switch away from source=("${_pkgname}/${_pkgname}-${pkgver}.tar.gz" ? The same question also applies to python-frida.