How to trace an error "Killed"

[chunrong]

Is there any way to know what happened when a "killed" is reported?

When I dealt with an apk (air.WatchESPN.apk) from google play, the output is as following:
"/home/test/Tools/redexer/scripts/../redexer -out tmp_dir_u3aadsiw/classes.dex tmp_dir_u3aadsiw/classes.dex -logging 2>&1
Killed
./scripts/cmd.rb:258:in `

': rewriting dex failed (RuntimeError)"

Thanks,

[kmicinski]

Hi Chunrong,

This is troubling indeed. One thing that you can do to diagnose the problem is to compile redexer with debugging symbols, and then set export OCAMLRUNPARAM=b to get the OCaml runtime to generate a stack trace. That would be helpful in isolating the problem.

To really diagnose the error, you will probably have to send it to someone on the redexer team and ask them to see what's going on.

[chunrong]

Hi Kmicinski,

Thanks for you quick reply! Can I send the apk to you? Or someone else on the great team?

Great thanks,

[kmicinski]

You can send it to me, but I probably won't get around to it for a few days
because I have other work right now. I might have a chance to look at it
later this week, and until then I would be able to give feedback with a
backtrace from redexer

kris

On Sun, Feb 8, 2015 at 8:20 PM, chunrong notifications@github.com wrote:

Hi Kmicinski,

Thanks for you quick reply! Can I send the apk to you? Or someone else on
the great team?

Great thanks,

—
Reply to this email directly or view it on GitHub
#11 (comment).