I ran the --debug flag with chromium and this is what I get.

chromium-browser --debug 2>&1 | tee gdb-chromium.txt
# Env:
#     LD_LIBRARY_PATH=/usr/lib/chromium-browser
#                
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
#            GTK_PATH=
# CHROMIUM_USER_FLAGS=
#      CHROMIUM_FLAGS=  --enable-pinch
/usr/bin/gdb /usr/lib/chromium-browser/chromium-browser -x 
/tmp/chromiumargs.7UrczA
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/chromium-browser/chromium-browser...Reading 
symbols from 
/usr/lib/debug/.build-id/1c/447ddfe5801b1e898e275d0a960370b691c768.debug...done.
done.
(gdb) handle SIG33 pass nostop noprint
Signal        Stop      Print   Pass to program Description
SIG33         No        No      Yes             Real-time event 33
(gdb) set pagination 0
(gdb) run http://localhost:3000
Starting program: /usr/lib/chromium-browser/chromium-browser 
http://localhost:3000
Cannot parse expression `.L1185 4@r4'.
warning: Probes-based dynamic linker interface failed.
Reverting to original interface.

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
/usr/bin/chromium-browser: line 230:  4342 Killed                  $GDB 
"$LIBDIR/$APPNAME" -x $tmpfile

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1702633

Title:
  Google chrome cannot start with Raspberry Pi 3 Ubuntu-Mate 16.04.2

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  [8278:8278:0706/155805.403422:ERROR:process_singleton_posix.cc(253)] 
readlink(/tmp/.org.chromium.Chromium.umUEz3/SingletonCookie) failed: Permission 
denied
  chromium-browser: pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs 
(thread->pid) == thread->tid' failed.
  Received signal 4 <unknown> 0000722083f6
  #0 0x000076e13d12 base::debug::StackTrace::StackTrace()
  #1 0x000076e13952 base::debug::StackTrace::StackTrace()
  #2 0x000076e13ffc <unknown>
  #3 0x000072208270 <unknown>
  #4 0x0000722083f6 abort
  [end of stack trace]
  Calling _exit(1). Core file will not be generated.
  chromium-browser: pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs 
(thread->pid) == thread->tid' failed.
  Received signal 4 <unknown> 0000722083f6
  #0 0x000076e13d12 base::debug::StackTrace::StackTrace()
  #1 0x000076e13952 base::debug::StackTrace::StackTrace()
  #2 0x000076e13ffc <unknown>
  #3 0x000072208270 <unknown>
  #4 0x0000722083f6 abort
  [end of stack trace]
  Calling _exit(1). Core file will not be generated.
  Received signal 4 <unknown> 0000761f8f76
  #0 0x000076e4cd12 base::debug::StackTrace::StackTrace()
  #1 0x000076e4c952 base::debug::StackTrace::StackTrace()
  #2 0x000076e4cffc <unknown>
  #3 0x000072241270 <unknown>
  [end of stack trace]
  Calling _exit(1). Core file will not be generated.
  chromium-browser: pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs 
(thread->pid) == thread->tid' failed.
  Received signal 4 <unknown> 0000722083f6
  #0 0x000076e13d12 base::debug::StackTrace::StackTrace()
  #1 0x000076e13952 base::debug::StackTrace::StackTrace()
  #2 0x000076e13ffc <unknown>
  #3 0x000072208270 <unknown>
  #4 0x0000722083f6 abort
  [end of stack trace]
  Calling _exit(1). Core file will not be generated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 59.0.3071.109-0ubuntu0.16.04.1289
  Uname: Linux 4.9.35-v7+ armv7l
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: armhf
  Date: Thu Jul  6 16:04:23 2017
  Desktop-Session:
   'None'
   'None'
   'None'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstalledPlugins:
   
  Load-Avg-1min: 1.10
  Load-Processes-Running-Percent:   0.5%
  Lspci:
   Error: command ['lspci', '-mmkv'] failed with exit code 1: pcilib: Cannot 
open /proc/bus/pci
   lspci: Cannot find any working access method.
  Lsusb:
   Bus 001 Device 005: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 004: ID 046d:c315 Logitech, Inc. Classic Keyboard 200
   Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
   Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: 8250.nr_uarts=0 bcm2708_fb.fbwidth=1360 
bcm2708_fb.fbheight=768 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3dc00000 
vc_mem.mem_size=0x3f000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 
console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline 
fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.chromium-browser.default: 
CHROMIUM_FLAGS="--ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so 
--ppapi-flash-version=25.0.0.148"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2017-06-03T11:44:06.716779

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702633/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to