You are not logged in.
Pages: 1
If I run
mitmproxy --mode local -v, it captures about 110 events and then it errors with
[linux-redirector] exited: Ok(ExitStatus(unix_wait_status(256))), and then stops capturing.
If I quit the TUI after this error happens, the following gets outputted:
FATAL: exception not rethrown
FATAL: exception not rethrown
FATAL: exception not rethrown
FATAL: exception not rethrown
Aborted (core dumped)And sometimes this:
Fatal Python error: PyGILState_Release: FATAL: exception not rethrown
Aborted (core dumped)I think the
Aborted (core dumped)message is SIGABRT in both cases.
Mitmproxy version: 11.1.3-2
Python version: 3.13.3-1
Last edited by marbens (2025-04-30 20:30:24)
Offline
This may be more suitable for Newbie Corner, as it doesn't seem testing-specific.
Offline
Moderator Note
Mitmproxy 11.1.3-2 entered [extra] repo yesterday, so testing board is no longer applicable .
Moving to NC as suggested.
Next time please use the report button (bottom right) to request a thread move.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I solved this problem by updating my system. Now it breaks DNS in local mode but that's a different problem.
Last edited by marbens (2025-04-30 20:31:11)
Offline
Pages: 1