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

Issue 596088 link

Starred by 3 users
Status: Fixed
Owner:
agrieve@chromium.org
Closed: Mar 2016
Cc:
█ aval...@chromium.org
yfried...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

adb_gdb uses the wrong target arch when running 32-bit chrome on a 64-bit device

Project Member Reported by agrieve@chromium.org, Mar 18 2016 
When this happens, GDB starts up, but often has garbage values.

Rather than query the device for its arch, we should get the arch from the app.

Comment 1 by youramer1@gmail.com, Mar 19 2016 

You

Comment 2 by youramer1@gmail.com, Mar 19 2016 

596088
Project Member

Comment 3 by bugdroid1@chromium.org, Mar 21 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/2e65b753af3feb69f69c35335db12526ff8d7220

commit 2e65b753af3feb69f69c35335db12526ff8d7220
Author: agrieve <agrieve@chromium.org>
Date: Mon Mar 21 17:36:13 2016

adb_gdb: Detect TARGET_ARCH from symbols_dir rather than device

This fixes arch detection when 32-bit Chrome is run on a 64-bit device

BUG= 596088 

Review URL: https://codereview.chromium.org/1811363002

Cr-Commit-Position: refs/heads/master@{#382319}

[modify] https://crrev.com/2e65b753af3feb69f69c35335db12526ff8d7220/build/android/adb_gdb

Comment 4 by agrieve@chromium.org, Mar 21 2016

Status: Fixed (was: Started)
►

Sign in to add a comment