You are not logged in.
Hi,
I am sticking to Gnome Web for aesthetic reasons (native app, loads faster and does what I need) except random crashes on certain websites.
Example sites:
1. Page: http://www.akitaonrails.com/2017/01/10/ … istro-ever
2. Go to http://www.omgubuntu.co.uk click on any post, wait until post fully loads:
Error:
Oops!
Something went wrong while displaying this page.
Please reload or visit a different page to continue.
Reload
Tried to find reason using gdb, terminal returned:
[me@my ~]# gdb /usr/bin/epiphany
GNU gdb (GDB) 8.0
Copyright (C) 2017 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 "x86_64-pc-linux-gnu".
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/bin/epiphany...(no debugging symbols found)...done.
(gdb) bt full
No stack.
(gdb) bt full
No stack.
Guides followed:
https://wiki.archlinux.org/index.php/St … ging_guide
https://wiki.archlinux.org/index.php/De … ing_Traces
Help needed:
Any suggestions to fix or drill this down further? And, is anyone else also facing similar problem?
Thanks
Last edited by jackpot (2017-06-19 19:44:18)
KDE is all good bloated, try to trim away from K*.apps... whatever it leaves behind equals "Kuck yourself!"
nVidia.... fsck sdy0
Offline
Inside gdb you first need to run the application and wait for the crash before trying to read the backtrace. Also you can check if a core dump was created, by typing coredumpctl list in a terminal. If that's the case, then you can view the dump with coredumpctl dump PID.
Offline
Offline
You can't use gdb on ArchLinux, Arch is missing debug packages :-/ Really an issue for me too.
Offline
And for information, I work on another browser for GNOME: https://gnumdk.github.io/eolie-web/
It will segfault too (as it's a webkit bug) but you may like it
Offline
@jackpot
Your output suggests that you are not very familiar with gdb. Please see a tutorial on using gdb. You need to run the application before getting the stack trace.
Type "run" and hit Enter before trying to get the trace using "bt full".
Also to get a meaningful trace you application needs to have debugging information in its binary. For that you need to recompile the software using information from: https://wiki.archlinux.org/index.php/St … gdb_output
Offline
Thank you for responses, spinnau and adesh for telling me about the need to recompile. gnumdk for suggesting Eolie (looks good, will try).
Reconsidering the bug being filed upstream, I will watch and wait till it gets fixed.
Reference:
https://bugs.webkit.org/show_bug.cgi?id=173539
https://bugs.webkit.org/show_bug.cgi?id=172754
Last edited by jackpot (2017-06-19 19:49:47)
KDE is all good bloated, try to trim away from K*.apps... whatever it leaves behind equals "Kuck yourself!"
nVidia.... fsck sdy0
Offline
You can't use gdb on ArchLinux, Arch is missing debug packages :-/ Really an issue for me too.
That is the most absurd assertion I have heard this year
ewaller@turing ~ 1024 %cd devel/C/crashGen
ewaller@turing ~/devel/C/crashGen 1025 %cat crashme.c
#include <stdlib.h>
#include <stdio.h>
int main (int argc, char ** argv)
{
int *foo = NULL;
char x;
printf("This should crash as we are about to write %i to address %i",argc,foo);
x=getchar();
*foo = argc; /* Boom ! */
}
ewaller@turing ~/devel/C/crashGen 1026 %gcc crashme.c -g
ewaller@turing ~/devel/C/crashGen 1027 %gdb a.out
GNU gdb (GDB) 8.0
Copyright (C) 2017 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 "x86_64-pc-linux-gnu".
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 a.out...done.
(gdb) run
Starting program: /home/ewaller/devel/C/crashGen/a.out
This should crash as we are about to write 1 to address 0
Program received signal SIGSEGV, Segmentation fault.
0x0000000000400565 in main (argc=1, argv=0x7fffffffdf98) at crashme.c:11
11 *foo = argc; /* Boom ! */
(gdb) bt
#0 0x0000000000400565 in main (argc=1, argv=0x7fffffffdf98) at crashme.c:11
(gdb) l
6 {
7 int *foo = NULL;
8 char x;
9 printf("This should crash as we are about to write %i to address %i",argc,foo);
10 x=getchar();
11 *foo = argc; /* Boom ! */
12 }
(gdb)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
@ewaller
No, you don't understand how it works... Sure it works with a self compiled software... But if you have a crash in webkitgtk on ArchLinux, your backtrace will be full of undefined symbols (and so unusable).
https://wiki.archlinux.org/index.php/De … ing_Traces
So, one solution, rebuild packages to know where the crash is but for webkitgtk, it means: build glib, gtk and webkitgtk... On my computer, 12 hours to finish compilation.
Offline