Closed Bug 1053146 Opened 10 years ago Closed 7 years ago

[flatfish][bluetooth] enabling bluetooth crashes settings with bluedroid

Categories

(Firefox OS Graveyard :: Bluetooth, defect)

Product:
Firefox OS Graveyard
Component:
Bluetooth
Platform:
ARM
Other
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: steve, Unassigned)

References

Details

Using the latest master source and the bluedroid image provided in #986314 (as directed in build error) the settings app closes when enabling bluetooth
I entered this bug on my flatfish expecting the browser tags to be included and hopefully including build details. As they are not here are the build details

OS 2.2.0.0-prerelease
firmware 2014812-2216
build 20140812222747
Hardware: Other → ARM
the latest master? See bug 1053107
Summary: [flatfish][bluetooth] enabling blue tooth crashes settings with bluedroid → [flatfish][bluetooth] enabling bluetooth crashes settings with bluedroid
(In reply to Shawn Huang [:shuang] [:shawnjohnjr] from comment #2)
> the latest master? See bug 1053107

Thanks. Any idea how to see such debug output on the Flatfish?
If you saw crash on Settings, can you gdb attach to Settings?
1. adb shell b2g-ps
2. Check something like this "(Preallocated a  2 u0_a1166  1166  336   61684  19136 ffffffff b6e6767c S /system/b2g/b2g", you will see PID 1166.
3. Under source code directory, execute ./run-gdb.sh attach 1166
1166 will be your Settings app PID.
4. Launch Settings app
5. You will have gdb prompt, and type "c"
Do something make it crash, and you will crash dump
(In reply to Shawn Huang [:shuang] [:shawnjohnjr] from comment #4)
> If you saw crash on Settings, can you gdb attach to Settings?
> 1. adb shell b2g-ps
> 2. Check something like this "(Preallocated a  2 u0_a1166  1166  336   61684
> 19136 ffffffff b6e6767c S /system/b2g/b2g", you will see PID 1166.
> 3. Under source code directory, execute ./run-gdb.sh attach 1166
> 1166 will be your Settings app PID.
> 4. Launch Settings app
> 5. You will have gdb prompt, and type "c"
> Do something make it crash, and you will crash dump

Thanks Will give it a go. I have general problems with ADB right now, so need to resolve them first.
I get this error

./run-gdb.sh: line 141: prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7/bin/arm-linux-androideabi-gdb: No such file or directory

Have I not installed or built something or is this a bug in the flatfish build? or doesn run-gdb need updating for flatfish?
I have arm-linux-androideabi-4.6 not arm-linux-androideabi-4.7
Ya, JB 4.2 uses toolchain 4.6, so you can modify run-gdb.sh, please replace 4.7 to 4.6.
 
GDB=prebuilts/gcc/${HOST_OS}/${TARGET_ARCH}/${TARGET_TRIPLE}-4.7/bin/${TARGET_TRIPLE}-gdb
Or do something like:
--- a/run-gdb.sh
+++ b/run-gdb.sh
@@ -14,6 +14,9 @@ if [ -z "${GDB}" ]; then
       GDB=prebuilt/$(uname -s | tr "[[:upper:]]" "[[:lower:]]")-x86/toolchain/arm-linux-androideabi-4.4.x/bin/arm-linux-androideabi-gdb
    elif [ -d prebuilts ]; then
       GDB=prebuilts/gcc/$(uname -s | tr "[[:upper:]]" "[[:lower:]]")-x86/arm/arm-linux-androideabi-4.7/bin/arm-linux-androideabi-gdb
+      if [ ! -f $GDB ] ; then
+               GDB=prebuilts/gcc/$(uname -s | tr "[[:upper:]]" "[[:lower:]]")-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gdb
+      fi
    else
       echo "Not sure where gdb is located. Override using GDB= or fix the script."
       exit 1
Thanks Shawn.

What is JB?

1) problem is then getting a missing dependency share lib, - see #1053346
2) Is this a global change for all configs or just for flatfish? If latter I need to figure how to do so?
See Also: → https://bugzilla.mozilla.org/show_bug.cgi?id=1053346
Depends on: 1053346
JB->Jelly Bean (Android 4.2)
1. Already added comments to install that library
2. You can just apply change as Comment 9 described
2) should I provide a patch or is that sorted?
The error causing settings to crash is

Program received signal SIGTERM, Terminated.
nsGlobalWindow::Release (this=0x43191d40)
    at ../../../gecko/dom/base/nsGlobalWindow.cpp:1684
1684	NS_IMPL_CYCLE_COLLECTING_RELEASE(nsGlobalWindow)
PS that's using todays build
I guess this is related to bug 1053107. Not only flatfish but also other devices can be seen Setting crash due to app ID invalid.
It could be regression of bug 1033951.
On the current 20140901 flatfish build, opening the "bluetooth" panel in settings causes the settings app to crash.
When tapping the Bluetooth option in settings page, the Settings app closes automatically.

* "Broken" Env. Info:
  Device  : Flatfish 2.1 Master
  B2G     : 2.1.0.0-prerelease
  Gaia    : e95cb37011fe9e0ea3ef83393687b9d1d54c3494
  Gecko   : c5b55f7c492664837cba920d256e8b54cc008de2
  BuildID : 20140901012406
  Version : 34.0a1

* "Working" Env. Info:
  Device  : Flatfish 2.1 Master
  B2G     : 2.1.0.0-prerelease
  Gaia    : 007f3c50cf69f044628a23c2376c6d88aa45f617
  Gecko   : 6ea8870876e62b440ed3c54c86ff6be9055d5015
  BuildID : 20140829012624
  Version : 34.0a1
Interesting as I had the problem BEFORE 20140829 as can be seen from the date of this bug. So it does seem like a regression.
(In reply to Shawn Huang [:shuang] [:shawnjohnjr] from comment #9)
> Or do something like:
> --- a/run-gdb.sh
> +++ b/run-gdb.sh
> @@ -14,6 +14,9 @@ if [ -z "${GDB}" ]; then
>        GDB=prebuilt/$(uname -s | tr "[[:upper:]]"
> "[[:lower:]]")-x86/toolchain/arm-linux-androideabi-4.4.x/bin/arm-linux-
> androideabi-gdb
>     elif [ -d prebuilts ]; then
>        GDB=prebuilts/gcc/$(uname -s | tr "[[:upper:]]"
> "[[:lower:]]")-x86/arm/arm-linux-androideabi-4.7/bin/arm-linux-androideabi-
> gdb
> +      if [ ! -f $GDB ] ; then
> +               GDB=prebuilts/gcc/$(uname -s | tr "[[:upper:]]"
> "[[:lower:]]")-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-
> gdb
> +      fi
>     else
>        echo "Not sure where gdb is located. Override using GDB= or fix the
> script."
>        exit 1

@Shawn what do I need to do to get this and the old Python library into the code base?
I guess I answer in other bug that you raised.
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.