ChanServ changed the topic of #reoxide to: Website: https://reoxide.eu Code: https://codeberg.org/ReOxide IRC Logs: https://irclog.reoxide.eu/reoxide
osogi has joined #reoxide
osogi has quit [Changing host]
osogi has joined #reoxide
<osogi> Hi,
<osogi> I'm having trouble launching your tool. `reoxided` hitting a segfault . It starts up okay, but crashes when something try to interact with it.
<osogi> I've included the simplest way to reproduce it below, but I'm seeing the same behavior in my actual use case.
<osogi> ---
<osogi> Env:
<osogi> ```
<osogi> (venv) user1@fridgeOS:~/my_bins/reoxide$ python --version
<osogi> Python 3.12.5
<osogi> (venv) user1@fridgeOS:~/my_bins/reoxide$ pip list
<osogi> Package      Version
<osogi> ------------ -------
<osogi> pip          24.2
<osogi> platformdirs 4.5.1
<osogi> PyYAML       6.0.3
<osogi> pyzmq        27.1.0
<osogi> reoxide      0.7.1
<osogi> (venv) user1@fridgeOS:~/my_bins/reoxide$ reoxide link-ghidra
<osogi> Checking Ghidra install at "/home/user1/my_bins/ghidra/ghidra_12.0_PUBLIC"
<osogi>               ^^^^^^^^^^^^^^^^
<osogi>   File "/home/user1/my_bins/reoxide/venv/lib/python3.12/site-packages/reoxide/manage/client.py", line 404, in list_plugins
<osogi>     raise TimeoutError()
<osogi> TimeoutError
<osogi> ```
<osogi> ---
<osogi> Any ideas what's up?
<osogi> If you need a proper issue I can make one, but I'm lazy about writing good bug reports.
<osogi> Thanks
osogi has quit [Quit: Client closed]
osogi has joined #reoxide
<cluosh> hmm let me check if I can reproduce
<cluosh> is that paste complete btw? because it's doing the link-ghidra, but that's unrelated to a `reoxided` segfault
<osogi> Yes, it completed. I'm just keeped `link-ghidra` because I'm not sure if it will be related or not. And it additionally provides information about ghidra version if needed.
<osogi> *i just keeped
<cluosh> Hmm are you sure IRC didn't cut off your logs? Because it only shows the TimeoutError in list_plugins, so I am assuming you ran `reoxide list-actions` or the GUI?
<cluosh> What is the output when you run `reoxided`?
<cluosh> The timeout error only shows that it wasn't able to connect to reoxided, which makes sense since you said reoxided crashed, but there is no log output of reoxided
<cluosh> If you have longer log snippets it's best to create an issue and paste them there, don't worry, it doesn't have to be a "proper" bug report :)
<osogi> > What is the output when you run `reoxided`?
<osogi> If only run `reoxided` (no interactions)
<osogi> ```
<osogi> (venv) user1@fridgeOS:~/my_bins/reoxide$ reoxided
<osogi> 2026-01-14T13:34:48 INFO reoxide - Restarting with updated LD_LIBRARY_PATH...
<osogi> 2026-01-14T13:34:48 INFO reoxide - Using data_dir: /home/user1/.local/share/reoxide
<osogi> 2026-01-14T13:34:48 INFO reoxide - Loading /home/user1/.local/share/reoxide/plugins/libcore.so
<osogi> ```
<osogi> If try to interact it. A segfault appears immediately.
<osogi> ```
<osogi> (venv) user1@fridgeOS:~/my_bins/reoxide$ reoxided
<osogi> 2026-01-14T13:34:48 INFO reoxide - Restarting with updated LD_LIBRARY_PATH...
<osogi> 2026-01-14T13:34:48 INFO reoxide - Using data_dir: /home/user1/.local/share/reoxide
<osogi> 2026-01-14T13:34:48 INFO reoxide - Loading /home/user1/.local/share/reoxide/plugins/libcore.so
<osogi> Segmentation fault (core dumped)
<osogi> ```
<osogi> If logs aren't supposed to be in stderr/stdout, I'd appreciate it if you could tell me how to get them correctly.
<osogi> > Hmm are you sure IRC didn't cut off your logs?
<osogi> Not sure, but there is not much of them
<osogi> > Because it only shows the TimeoutError in list_plugins, so I am assuming you ran `reoxide list-actions` or the GUI?
<osogi> Got the pretty same output for list-actions and list-rules (no gui).
<osogi> ```
<osogi> (venv) user1@fridgeOS:~/my_bins/reoxide$ reoxide list-actions
<osogi> Traceback (most recent call last):
<osogi>   File "/home/user1/my_bins/reoxide/venv/bin/reoxide", line 8, in <module>
<osogi>     sys.exit(client_cli())
<osogi>              ^^^^^^^^^^^^
<osogi>   File "/home/user1/my_bins/reoxide/venv/lib/python3.12/site-packages/reoxide/reoxide.py", line 358, in client_cli
<osogi>     args.func(
<osogi>   File "/home/user1/my_bins/reoxide/venv/lib/python3.12/site-packages/reoxide/manage/cli.py", line 10, in cmd_list_actions
<osogi>     plugins = c.list_plugins()
<osogi>               ^^^^^^^^^^^^^^^^
<osogi>   File "/home/user1/my_bins/reoxide/venv/lib/python3.12/site-packages/reoxide/manage/client.py", line 404, in list_plugins
<osogi>     raise TimeoutError()
<osogi> TimeoutError
<cluosh> Okay that is really strange
<cluosh> `reoxided` is a Python program, it's not supposed to segfault :) I guess it must be related to the dlopen of the `libcore.so` plugin but I have not seen this behavior before
<cluosh> what architecture and OS are you on?
<osogi> OS: Ubuntu MATE 22.04.5 LTS x86_64
<osogi> Kernel: 6.8.0-52-generic
<cluosh> Thank you. I will set up a VM and try to reproduce later today
<cluosh> do you happen to have a coredump of that segfault?
<osogi> By the way, this isn't urgent and might not even be necessary. I still wanted to try https://github.com/thixotropist/ghidra_decompiler_plugins
<cluosh> osogi: Thank you, I saved the coredump
<cluosh> And yes, but it is a bit urgent for me, since I want to make sure to provide a good plug-and-play experience and if it fails on a pretty standard Linux system I want to fix that as soon as possible :D
<cluosh> One last thing; is that just the stock setup or did you add any other plugins yet?
osogi has quit [Ping timeout: 272 seconds]
<cluosh> I can reproduce, opened an issue for tracking: https://codeberg.org/ReOxide/reoxide/issues/12
osogi has joined #reoxide
<osogi> > One last thing; is that just the stock setup or did you add any other plugins yet?
<osogi> Sorry for the long reply, I was away.
<osogi> Yes, it's a stock environment with no additional plugins. Although it seems like that's irrelevant now, and you figured it out yourself.
osogi has quit [Quit: Client closed]
<cluosh> if CI goes through I will push a release
osogi has joined #reoxide
<osogi> Yeah! Thank you, now it's working!
osogi has quit [Client Quit]