Test results for D on Android/ARM

Jakob Ovrum via digitalmars-d-ldc digitalmars-d-ldc at puremagic.com
Wed Nov 11 19:46:04 PST 2015


On Sunday, 8 November 2015 at 09:49:18 UTC, Joakim wrote:
> They're both related to accessing files, whether a socket file 
> or a symbolic link.  Given that they pass from the apk, my 
> guess is that this is related to user/file permissions because 
> you're running as root from the Download directory.  Can you 
> try running as a normal user in the local folder for SSHDroid, 
> as described here?
>
> http://wiki.dlang.org/Build_LDC_for_Android#Run_the_druntime_and_phobos_unit_tests

Running it as root in the home directory 
(/data/data/berserker.android.apps.sshdroid/home) fixed those 
errors. I don't know how to add non-root users though.

> With some builds, I used to get an issue with core.thread 
> interacting with the static destructor for std.parallelism, 
> which would cause a segfault on exit.  This could be that issue.
>
> As for debugging, the NDK comes with an ARM gdb server, found 
> in prebuilt/android-arm/gdbserver/gdbserver, which you can use 
> with their gdb to remotely debug Android apps.

Thanks, I got gdb-server running. In core.thread and some later 
modules it stops because of SIGUSR1 and SIGUSR2; I guess I should 
make gdb ignore those? After continuing from all the SIGUSR 
signals, I get the segfault that occurs after 
std.internal.math.gammafunction passes:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 22658.22658]
0x4250a364 in core.thread.Thread.getAll() ()
(gdb) bt
#0  0x4250a364 in core.thread.Thread.getAll() ()
#1  0x43236e04 in std.parallelism._sharedStaticDtor7() ()
#2  0x42549758 in rt.minfo.rt_moduleDtor() ()
#3  0x42557e70 in rt_term ()
#4  0x42558120 in _d_run_main ()
#5  0x43e85418 in ?? ()
Backtrace stopped: previous frame identical to this frame 
(corrupt stack?)
(gdb) info threads
   Id   Target Id         Frame
* 1    Thread 22658.22658 0x4250a364 in 
core.thread.Thread.getAll() ()

I'm guessing this is the same issue you mentioned.


More information about the digitalmars-d-ldc mailing list