Re: [dev] [surf] segmentation fault
m...@datameer.com wrote: > yea, I should do it. The thing is I didn't run into a crash with firefox > or vimb. just for correctness. i was running into the same thing with vimb (they catch the error and do not crash at all) so it is obvisuosly a webkit issue. thx marko
Re: [dev] [surf] segmentation fault
Страхиња Радић wrote: > On 22/01/13 11:52, m...@datameer.com wrote: > Why don't you just try it and find out? I did it and i'm getting the same issue. > If you are asking me about my personal experience, I always compile surf from > source. yes, i was more interrested into personal experience. my fault, next time i will ask more accurate. > ...If the binary version of wekbit doesn't work, > the only other thing you can try is compile it from source. yea, I should do it. The thing is I didn't run into a crash with firefox or vimb. anyway, i will try to compile webkit as well. thx marko
Re: [dev] [surf] segmentation fault
On 22/01/13 11:52, m...@datameer.com wrote: > Regarding the note on the website `Compile your own webkit or expect > hell`... > Is it better or more stable to compile webkit as well? Why don't you just try it and find out? If you are asking me about my personal experience, I always compile surf from source. I maintain my own personal fork with my choice of patches and customizations at [1]. I never had any problems yet on Artix with compiling and using surf with Artix's precompiled webkit. When using binary packages, you are at the mercy of however the maintainers of your distro decided to compile it. When you compile software from source, you have (more) control over how the software is compiled. If the binary version of wekbit doesn't work, the only other thing you can try is compile it from source. If that fails too, raise the issue with the maintainers of your distro. [1]: https://git.sr.ht/~strahinja/surf signature.asc Description: PGP signature
Re: [dev] [surf] segmentation fault
m...@datameer.com wrote: > Does that mean I have to compile surf incl all dependencies with > https://github.com/void-linux/void-packages? > > Or do you have any other hint for me? Страхиња did show you the way : config.h is the user configuration file, distributions might also want packages with reasonable config.h letting other packages putting dependencies on i.e. surf, dmenu, st... Given the error message: > segfault at 570 ip 7f3e80b76a34 sp 7ffce08e3148 error 4 in > libwebkit2gtk-4.0.so.37.55.5[7f3e806d+2387000] If you feel like there is something going wrong at surf level rather than webkit itself (such as wrong use or configuration of webkit), comparing how webkit is used in another browser could tell. Another thing to try: first compiling surf from git with the packaged webkit you already have, then check again to see if it still carshes. This will tell if the bug can be fixed on surf or webkit level.
Re: [dev] [surf] segmentation fault
Страхиња Радић wrote: > Compiling from source is the intended way to use suckless software. > > Suckless software is configured by editing config.h, rather than by using > configuration files. Yes, i'm used to compile my suckless software setup (when i have patches). In this case I hadn't patches. So ok, I will compile it. Regarding the note on the website `Compile your own webkit or expect hell`... Is it better or more stable to compile webkit as well? thx marko
Re: [dev] [surf] segmentation fault
On 22/01/12 04:02, m...@datameer.com wrote: > Does that mean I have to compile surf incl all dependencies with > https://github.com/void-linux/void-packages? Compiling from source is the intended way to use suckless software. Suckless software is configured by editing config.h, rather than by using configuration files. signature.asc Description: PGP signature
[dev] [surf] segmentation fault
Hi, I'm using voidlinux, dwm, st, dmenu. I would like to start using surf as my daily web browser. So I installed the binary verion from the package manager. `surf-2.1_1` and `webkit2gtk-2.34.2_1`. After some seconds or minutes of browsing the surf process terminates with ``` web process terminated: crashed zsh: segmentation fault surf google.de ``` and the log contains ``` 2022-01-12T14:37:23.16689 kern.info: [193408.198059] surf[14660]: segfault at 570 ip 7f3e80b76a34 sp 7ffce08e3148 error 4 in libwebkit2gtk-4.0.so.37.55.5[7f3e806d+2387000] 2022-01-12T14:37:23.16694 kern.info: [193408.198073] Code: 84 00 00 00 00 00 48 8d 15 c4 5a f2 01 48 8d 35 82 75 f2 01 31 ff e8 ab ad b6 ff 31 c0 5b c3 0f 1f 80 00 00 00 00 48 8b 47 30 <40> 38 b0 f0 00 00 00 74 2b 55 48 8b 2d 13 4e b7 02 40 88 b0 f0 00 ``` I read the section `Note On Webkit Versions` on https://surf.suckless.org/ Does that mean I have to compile surf incl all dependencies with https://github.com/void-linux/void-packages? Or do you have any other hint for me? thx marko -- Marko Bauhardt Datameer GmbH e. m...@datameer.com w. http://www.datameer.com/ a. Magdeburger Straße 23, 06112 Halle (Saale), Amtsgericht Stendal, HRB: 10348 Geschäftsführer: Frank Henze Request Datameer Spectrum Demo: https://bit.ly/38IlOe5
Re: [dev] surf segmentation fault
> Hi, Hi Joachim, > surf crashes with segmentation fault when opening http://dhl.de > This only happens on 32 bit systems (Debian Jessie). > > I compiled the latest version from git with symbols and did a > backtrace under gdb: > > Program received signal SIGSEGV, Segmentation fault. > 0xaa5c5a00 in ?? () > (gdb) backtrace > #0 0xaa5c5a00 in ?? () > #1 0xfffb in ?? () > #2 0xae3d99c0 in ?? () > #3 0xaa5c59eb in ?? () > #4 0xabc51f1c in ?? () > #5 0xb50b298b in ?? () from > /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 > #6 0xb50b298b in ?? () from > /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 > #7 0xb50b2aaf in ?? () from > /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 > #8 0xb50b298b in ?? () from > /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 > #9 0xb50b298b in ?? () from > /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 > #10 0xb50b298b in ?? () from > /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 > #11 0xb50af3e9 in ?? () from > /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 > #12 0xb504b806 in JSC::JITCode::execute(JSC::VM*, > JSC::ProtoCallFrame*, JSC::Register*) () from > /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 > #13 0xb502993f in JSC::Interpreter::executeCall(JSC::ExecState*, > JSC::JSObject*, JSC::CallType, JSC::CallData const&, JSC::JSValue, > JSC::ArgList const&) () from > /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 > #14 0xb516d234 in JSC::call(JSC::ExecState*, JSC::JSValue, > JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList > const&) () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 > #15 0xb62d2a86 in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #16 0xb64a9b3d in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #17 0xb64a9ffe in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #18 0xb64bb96d in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #19 0xb64a38d4 in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #20 0xb64a5bd2 in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #21 0xb64bf145 in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #22 0xb646ede5 in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #23 0xb66a2e8c in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #24 0xb66cf3d4 in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #25 0xb66a9540 in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #26 0xb66a9591 in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #27 0xb66abfd5 in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #28 0xb66a9abf in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #29 0xb66acc22 in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #30 0xb66accd1 in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #31 0xb67facbf in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #32 0xb67faa76 in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #33 0xb6807838 in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #34 0xb6865976 in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #35 0xb685b005 in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #36 0xb70d972d in ?? () from > /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 > #37 0xb549a9f5 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 > #38 0xb54c12e7 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 > #39 0xb54c131b in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 > #40 0xb4c38510 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 > #41 0xb4c3bcc3 in g_main_context_dispatch () from > /lib/i386-linux-gnu/libglib-2.0.so.0 > #42 0xb4c3c0d9 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 > #43 0xb4c3c489 in g_main_loop_run () from > /lib/i386-linux-gnu/libglib-2.0.so.0 > #44 0xb5b9b1b5 in gtk_main () from > /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 > #45 0x0804f5aa in main () This only shows the issue happen inside webkitgtk, surf has no handle on that. You could try it with another browser based on webkit1, if you can find one and it should hit the same problem. My advise is to try with surf-webkit2, based on webkit2 because webkit1 is deprecated anyway. Good luck!
Re: [dev] surf segmentation fault
I can reproduce bug on Debian. Just did a git clone git://git.suckless.org/surf then make. ~> cat /etc/debian_version 8.7 ~> uname -a Linux t400 3.16.0-4-686-pae #1 SMP Debian 3.16.39-1+deb8u1 (2017-02-22) i686 GNU/Linux ~/a/surf> ./surf -p http://dhl.de Vector smash protection is enabled. java version "1.7.0_121" OpenJDK Runtime Environment (IcedTea 2.6.8) (7u121-2.6.8-2~deb8u1) OpenJDK Server VM (build 24.121-b00, mixed mode) fish: “./surf -p http://dhl.de” terminated by signal SIGSEGV (Address boundary error) But when I disable Javascript, no crash: ~/a/surf> ./surf -ps http://dhl.de Vector smash protection is enabled. java version "1.7.0_121" OpenJDK Runtime Environment (IcedTea 2.6.8) (7u121-2.6.8-2~deb8u1) OpenJDK Server VM (build 24.121-b00, mixed mode)
[dev] surf segmentation fault
Hi, surf crashes with segmentation fault when opening http://dhl.de This only happens on 32 bit systems (Debian Jessie). I compiled the latest version from git with symbols and did a backtrace under gdb: Program received signal SIGSEGV, Segmentation fault. 0xaa5c5a00 in ?? () (gdb) backtrace #0 0xaa5c5a00 in ?? () #1 0xfffb in ?? () #2 0xae3d99c0 in ?? () #3 0xaa5c59eb in ?? () #4 0xabc51f1c in ?? () #5 0xb50b298b in ?? () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 #6 0xb50b298b in ?? () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 #7 0xb50b2aaf in ?? () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 #8 0xb50b298b in ?? () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 #9 0xb50b298b in ?? () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 #10 0xb50b298b in ?? () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 #11 0xb50af3e9 in ?? () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 #12 0xb504b806 in JSC::JITCode::execute(JSC::VM*, JSC::ProtoCallFrame*, JSC::Register*) () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 #13 0xb502993f in JSC::Interpreter::executeCall(JSC::ExecState*, JSC::JSObject*, JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&) () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 #14 0xb516d234 in JSC::call(JSC::ExecState*, JSC::JSValue, JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&) () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 #15 0xb62d2a86 in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #16 0xb64a9b3d in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #17 0xb64a9ffe in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #18 0xb64bb96d in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #19 0xb64a38d4 in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #20 0xb64a5bd2 in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #21 0xb64bf145 in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #22 0xb646ede5 in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #23 0xb66a2e8c in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #24 0xb66cf3d4 in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #25 0xb66a9540 in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #26 0xb66a9591 in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #27 0xb66abfd5 in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #28 0xb66a9abf in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #29 0xb66acc22 in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #30 0xb66accd1 in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #31 0xb67facbf in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #32 0xb67faa76 in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #33 0xb6807838 in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #34 0xb6865976 in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #35 0xb685b005 in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #36 0xb70d972d in ?? () from /usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0 #37 0xb549a9f5 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 #38 0xb54c12e7 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 #39 0xb54c131b in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 #40 0xb4c38510 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #41 0xb4c3bcc3 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #42 0xb4c3c0d9 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #43 0xb4c3c489 in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0 #44 0xb5b9b1b5 in gtk_main () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 #45 0x0804f5aa in main () ___
Re: [dev] [surf] Segmentation fault when clicking border
$ G_DEBUG=fatal-criticals gdb ./surf (gdb) cont ... (gdb) bt Backtrace from clicking anywhere on the window border of surf under dwm: #0 0xb71ae968 in _gdk_windowing_got_event () from /usr/lib/libgdk-x11-2.0.so.0 #1 0xb71cae47 in _gdk_events_queue () from /usr/lib/libgdk-x11-2.0.so.0 #2 0xb71cb1c0 in gdk_event_dispatch () from /usr/lib/libgdk-x11-2.0.so.0 #3 0xb6e7d378 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #4 0xb6e80bf0 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #5 0xb6e8105f in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #6 0xb73567d9 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #7 0x0804cf99 in main (argc=1, argv=0xb564) at surf.c:849 This is surf 0.3 with a couple patches to bind mouse buttons to stuff like back/forward in the history. Jon.
Re: [dev] [surf] Segmentation fault when clicking border
That's a corner case ;) On Jan 29, 2010, at 9:00 AM, Jonathan Slark jonathan.sl...@talktalk.net wrote: I'm running surf under dwm. I accidently clicked it's border and *womph* it disapeared! I ran surf from a terminal so I could see any output and repeated the click, it did the same thing saying there was a segmentation fault. Other windows in dwm don't seem to have the same problem; if I click urxvt's border it doesn't crash. Jon.
Re: [dev] [surf] Segmentation fault when clicking border
can't reproduce on 32bit/64bit. 2010/1/29 pancake panc...@youterm.com: That's a corner case ;) On Jan 29, 2010, at 9:00 AM, Jonathan Slark jonathan.sl...@talktalk.net wrote: I'm running surf under dwm. I accidently clicked it's border and *womph* it disapeared! I ran surf from a terminal so I could see any output and repeated the click, it did the same thing saying there was a segmentation fault. Other windows in dwm don't seem to have the same problem; if I click urxvt's border it doesn't crash. Jon. -- http://gnuffy.chaotika.org - Real Community Distro
Re: [dev] [surf] Segmentation fault when clicking border
That's a corner case ;) An edge case surely. Jon.
Re: [dev] [surf] Segmentation fault when clicking border
$ G_DEBUG=fatal-criticals gdb ./surf (gdb) cont ... (gdb) bt Evgeny Grablyk wrote: I tried this on Arch linux x64, surf-hg. It did not segfault, but produced these warnings on each border click: (unknown:31278): Gdk-CRITICAL **: gdk_window_get_events: assertion `GDK_IS_WINDOW (window)' failed (unknown:31278): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (unknown:31278): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed I have also seen such warnings with a GTK app I wrote when its border was clicked. I was not able to find any related information.
Re: [dev] [surf] segmentation fault
2009/10/31 Lorenzo Bolla lbo...@gmail.com: Hi all, I've tried to compile the latest surf version with libwebkit-1.1.15.3-1 and gtk-1.2.10-9. Compilation went fine, but running surf from the command line gets me a Segmentation fault. Any hints? I'm running Arch Linux 2.6.31-ARCH I tried to reproduce these crashes on ubuntu jaunty system yesterday with a custom glib 2.22, gtk-2.18 and webkit 1.1.15.3 build /usr/local/lib. It didn't crash for me when running it as follows: LD_LIBRARY_PATH=/usr/local/lib:/usr/lib ./surf So I'm a bit puzzled it worked for me without any issues and other telling me they tracked it down into enchant's dbus behavior or something. Is this arch linux related I wonder? Kind regards, Anselm
Re: [dev] [surf] segmentation fault
On Sat, Oct 31, 2009 at 06:49:07PM +, Anselm R Garbe wrote: So I'm a bit puzzled it worked for me without any issues and other telling me they tracked it down into enchant's dbus behavior or something. Is this arch linux related I wonder? As already said in a earlier thread, my arch has this behaviour too. Regards Moritz
Re: [dev] [surf] segmentation fault
On Sat, Oct 31, 2009 at 1:03 PM, Lorenzo Bolla lbo...@gmail.com wrote: Hi all, I've tried to compile the latest surf version with libwebkit-1.1.15.3-1 and gtk-1.2.10-9. Try using gtk2. Webkit requires a very recent version of gtk2. -- # Kurt H Maier
