[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[RP] Ratpoison cause segmentation fault while using it in Userland for A

From: Mgr. Janusz Chmiel
Subject: [RP] Ratpoison cause segmentation fault while using it in Userland for Android
Date: Sun, 8 Sep 2019 22:10:06 +0200
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4

Dear C language specialists here.
I AM offering exciting development mission to you. May be that you know about it. But Userland is very promising project, which allows users to run Linux distributions by using non rooted Android device. Sure. Linux run its userspace variant, but developers of Userland have done their best to support Unix sockets, Dbus and even dynamic shared memory and shared memory support in general. I will let The decision on you. If you could look deeply at The source code of Ratpoison, its dependent .h header files. Could you try to extend Ratpoison source code lines so it would not display segmentation fault message when running ratpoison in Userland session? I Am running Debian ARM64 Bit variant. But I Am using 64 Bit CPU and Android run 32 Bit. It is standard of many Android devices, because 64 Bit Android code allocates much more RAm and internal device storage. If you will decide, that working in this non standard environment is The waste of time, I will respect it. But Ratpoison is very light weight window manager and it would be ideal for such non standard environment such as Userland project. The interesting think is that even some C related library display segmentation fault, there is no other crash and Window manager work here. Do you think that I can simply ignore this, or is The segmentation fault The severe C language run-time bug, which can cause unexpected app behaviour and can cause whole system instability if I will run Ratpoison with this bug for A too long time?
Thank you very very much for yours thinkink and discussion.
With warmest regards.
Janusz Chmiel

reply via email to

[Prev in Thread] Current Thread [Next in Thread]