Closed Bug 819052 Opened 12 years ago Closed 12 years ago

JimDB not usable for C++ Android unit tests when invoked manually

Categories

(Firefox for Android Graveyard :: JimDB, defect)

x86
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: dmosedale, Unassigned)

Details

In particular, if I invoke jimdb-gdbserver by hand on Android:

../../jimdb-gdbserver  :5039 ./signaling_unittests
Process ./signaling_unittests created; pid = 3969
Listening on port 5039
Remote debugging from host 10.250.3.129

and then if I take the copy of JimDB and invoke it by hand: 

  JimDB ./signaling_unittests 

I got a bunch of (what I believe to be superfluous) Python errorage.  Then, when I attach:

Reading symbols from /Users/dmose/r/inbound/objdir-droid/dist/bin/signaling_unittests...done.
(gdb) target remote 10.250.7.4:5039
Remote debugging using 10.250.7.4:5039
Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response
warning: Remote failure reply: E01
Ignoring packet error, continuing...
Malformed response to offset query, timeout

It appears to have deeper debugging protocol problems shown above and eventually times out.
This was really just a workaround for bug 818301, so I'm removing [android-dev-pain], since it's no longer in the critical path.  On the theory that 818301 is plenty good enough, I'm going to resolve WONTFIX.  Jim, feel free to re-open if you disagree.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Whiteboard: [android-dev-pain]
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.