New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 754519 link

Starred by 0 users

Issue metadata

Status: Duplicate
Owner: ----
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Crash during host scan

Project Member Reported by khorimoto@chromium.org, Aug 11 2017

Issue description

I'm currently testing with 3 potential host devices.

Unfortunately, when a crash occurs, gdb does not stop like it normally does on a crash. Instead, it just repeats the warning logs listed below forever and ever until you stop gdb. I'm not sure how to get a full stack trace, but when the crash starts, I do see a reference to bluetooth_low_energy_weave_client_connection, which leads me to believe the crash is originating in that class.

GDB output below:

[Thread 0x9574a430 (LWP 8148) exited]
[Thread 0x9734b430 (LWP 8066) exited]
[Thread 0xb1943430 (LWP 8058) exited]
[Thread 0x9e539430 (LWP 7970) exited]
[Thread 0x9fdab430 (LWP 7967) exited]
[Thread 0xa05ab430 (LWP 7966) exited]
[Thread 0xa2e3a430 (LWP 7935) exited]
[Thread 0xaaa8c430 (LWP 7900) exited]
[New Thread 0xaaa8c430 (LWP 8198)]
[Thread 0xad28c430 (LWP 7895) exited]
[Thread 0xaca8c430 (LWP 7896) exited]
[New Thread 0xaca8c430 (LWP 8199)]
[Thread 0xab28c430 (LWP 7899) exited]
[New Thread 0xab28c430 (LWP 8200)]
[New Thread 0xad28c430 (LWP 8201)]
[New Thread 0x9fdab430 (LWP 8202)]
[New Thread 0x9e539430 (LWP 8203)]
[New Thread 0xb1943430 (LWP 8215)]
[Thread 0xb1943430 (LWP 8215) exited]
[New Thread 0xb1943430 (LWP 8233)]
[Thread 0x9cce3430 (LWP 7973) exited]
[Thread 0x94f4a430 (LWP 8165) exited]
[Thread 0xac28c430 (LWP 7897) exited]
[Thread 0x9dd1d430 (LWP 7971) exited]
[Thread 0xad28c430 (LWP 8201) exited]
[Thread 0xaaa8c430 (LWP 8198) exited]
[Thread 0xa0dcc430 (LWP 7965) exited]
[Thread 0xb1943430 (LWP 8233) exited]
warning: Could not find DWO CU obj/components/cryptauth/ble/ble/bluetooth_low_energy_weave_client_connection.dwo(0x992b1b83f9e73eba) referenced by CU at offset 0xd8fbb [in module /opt/google/chrome/chrome]
warning: (Internal error: pc 0x38b1df14 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x38b1dda0 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x38b1df14 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x38b1df14 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x38b1df14 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x38b1dda0 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x38b1df14 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x38b1df14 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x38b1df14 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x38b1dda0 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x38b1df14 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x38b1df14 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x38b1df14 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x38b1dda0 in read in psymtab, but not in symtab.)

 
Mergedinto: 756174
Status: Duplicate (was: Untriaged)
I'm fairly certain that this was issue 756174.

Sign in to add a comment