NaCl module debugging is not working in Chrome 49
Reported by
sergey.s...@gmail.com,
Apr 2 2016
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 Steps to reproduce the problem: 1. Set Chrome path env variable to the Chrome executable path, e.g. set CHROME_PATH=C:\Program Files (x86)\Google\Chrome\Application\chrome.exe 2. Build and run the example "Graphics 2D" from NaCl SDK (<nacl_sdk>/pepper_49/examples/api/graphics_2d) with the following command: make debug 3. In the gdb window that will appear issue issue the following command: target remote :4014 What is the expected behavior? The gdb will connect and after entering continue you will be able to observe the app running showing simulated flame. What went wrong? The following error message appears: Status: ERROR [NaCl module load failed: Nexe crashed during startup] Did this work before? Yes It is working in Chrome version 44 Chrome version: Version 49.0.2623.110 m Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 21.0 r0
,
Apr 3 2016
,
Apr 4 2016
,
Apr 4 2016
It doesn't related to Chrome DevTools.
,
Apr 5 2016
Could this be caused by the --no-sandbox flag? NativeClient: NaCl's GDB debug stub requires --no-sandbox flag on Windows. See crbug.com/265624.
,
Apr 6 2016
The following revision refers to this bug: https://chromium.googlesource.com/native_client/src/native_client.git/+/f84b2da442c06eb324212042970520dc2fcc5e80 commit f84b2da442c06eb324212042970520dc2fcc5e80 Author: bradnelson <bradnelson@chromium.org> Date: Wed Apr 06 21:22:11 2016 Revert "Debug Stub: Added support for windows in ipc_transport." This change actually ended up breaking nacl debugging on windows. It turns on what was intended to be the new debugging path without keeping the old path sufficiently working. We had intended to direct windows debugging a pipe, however, the chrome side change never landed due to other issues. BUG= chromium:600103 R=binji@chromium.org,mcgrathr@chromium.org This reverts commit d8c34ff8a79c5e6e385f3b39534220090d64e019. Review URL: https://codereview.chromium.org/1867633002 [modify] https://crrev.com/f84b2da442c06eb324212042970520dc2fcc5e80/src/public/chrome_main.h [modify] https://crrev.com/f84b2da442c06eb324212042970520dc2fcc5e80/src/trusted/debug_stub/build.scons [modify] https://crrev.com/f84b2da442c06eb324212042970520dc2fcc5e80/src/trusted/debug_stub/transport_ipc.cc [modify] https://crrev.com/f84b2da442c06eb324212042970520dc2fcc5e80/src/trusted/debug_stub/transport_ipc_test.cc [modify] https://crrev.com/f84b2da442c06eb324212042970520dc2fcc5e80/src/trusted/service_runtime/nacl_debug_init.h [modify] https://crrev.com/f84b2da442c06eb324212042970520dc2fcc5e80/src/trusted/service_runtime/sel_main_chrome.c
,
Apr 11 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/9d2c904a4638a6aa6ab690def90071f171d29eb1 commit 9d2c904a4638a6aa6ab690def90071f171d29eb1 Author: nacl-deps-roller <nacl-deps-roller@chromium.org> Date: Mon Apr 11 06:45:41 2016 Roll src/native_client/ bdf73e78f..0fdb5d2bc (2 commits). https://chromium.googlesource.com/native_client/src/native_client.git/+log/bdf73e78fc50..0fdb5d2bc6f3 $ git log bdf73e78f..0fdb5d2bc --date=short --no-merges --format='%ad %ae %s' 2016-04-06 pcc Disable -fwhole-program-vtables when compiling nacl_bootstrap_lib. 2016-04-06 bradnelson Revert "Debug Stub: Added support for windows in ipc_transport." BUG= 580389 , 600103 CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_chromium_dbg_32_ng,linux_nacl_sdk_build TBR=mseaborn@chromium.org Review URL: https://codereview.chromium.org/1876693002 Cr-Commit-Position: refs/heads/master@{#386342} [modify] https://crrev.com/9d2c904a4638a6aa6ab690def90071f171d29eb1/DEPS
,
Apr 18 2016
I use kubuntu 14.04 with chrome 50.0.2661.75 and kubuntu 15.10 with chrome 49.0.2623.112 and none of these works with enable-nacl-debug flag.
,
Aug 9 2016
matetuske@ could you please confirm whether the issue exist in latest chrome Stable- 52.0.2743.116?
,
Aug 15 2016
I tried it now in a debian, and the issue still exists in the leastest stable version
,
Aug 15 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by cbiesin...@chromium.org
, Apr 3 2016