Closed
Bug 976478
Opened 10 years ago
Closed 10 years ago
B2G NFC: emulator crashed when running test_nfc_manager_tech_discovered marionettet test.
Categories
(Firefox OS Graveyard :: NFC, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 970263
People
(Reporter: allstars.chh, Assigned: allstars.chh)
References
Details
[New Thread 0x7f5226264700 (LWP 19049)] [New Thread 0x7f522513d700 (LWP 19065)] [Thread 0x7f522513d700 (LWP 19065) exited] Program received signal SIGABRT, Aborted. 0x00007f52668fa425 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 64 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007f52668fa425 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x00007f52668fdb8b in __GI_abort () at abort.c:91 #2 0x00007f52668f30ee in __assert_fail_base (fmt=<optimized out>, assertion=0x63ed20 "rfst != NUMBER_OF_NFC_RFSTS", file=0x63eceb "external/qemu/hw/nfc-nci.c", line=<optimized out>, function=<optimized out>) at assert.c:94 #3 0x00007f52668f3192 in __GI___assert_fail (assertion=0x63ed20 "rfst != NUMBER_OF_NFC_RFSTS", file=0x63eceb "external/qemu/hw/nfc-nci.c", line=1053, function=0x642d20 <__PRETTY_FUNCTION__.7938> "nfc_create_rf_intf_activated_ntf") at assert.c:103 #4 0x00000000004c2334 in nfc_create_rf_intf_activated_ntf (re=0x8a8c80 <nfc_res>, nfc=0xc560a0 <_nfc_states+4160>, ntf=0xc553a4 <_nfc_states+836>) at external/qemu/hw/nfc-nci.c:1053 #5 0x00000000004bf252 in goldfish_nfc_send_ntf (create=<optimized out>, data=<optimized out>) at external/qemu/hw/goldfish_nfc.c:291 #6 0x000000000041bff3 in do_nfc_ntf (client=<optimized out>, args=<optimized out>) at external/qemu/android/console.c:3275 #7 0x000000000041e891 in control_client_do_command (client=0x2bfbab0) at external/qemu/android/console.c:453 #8 control_client_read_byte (ch=<optimized out>, client=0x2bfbab0) at external/qemu/android/console.c:539 #9 control_client_read (_client=0x2bfbab0) at external/qemu/android/console.c:597 #10 0x0000000000463d96 in qemu_iohandler_poll (readfds=0x7fff12892ad0, writefds=0x7fff12892b50, xfds=<optimized out>, ret=<optimized out>) at external/qemu/iohandler.c:120 #11 0x0000000000417a22 in main_loop_wait (timeout=0) at external/qemu/vl-android.c:1955 #12 0x000000000041a301 in main_loop () at external/qemu/vl-android.c:2012 #13 qemu_main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at external/qemu/vl-android.c:4528 #14 0x0000000000407736 in main (argc=-1, argv=0x7fff128967e8) at external/qemu/android/main.c:1303
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → allstars.chh
Comment 1•10 years ago
|
||
The emulator is not in 'Discovery' state. I've usually seen this when there have been modifications to nfcd that changed the init sequence of the device. Another thing could be a triggered timeout in the test script. Does it work if yo run the test's steps by hand?
Assignee | ||
Comment 2•10 years ago
|
||
Thanks for the info, Thomas. It should be related to Bug 970263.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•