GNOME Bugzilla – Bug 697921
Crash when try to create a new note in 32 bits version
Last modified: 2013-04-20 00:19:22 UTC
I've try it in Arch Linux since a few months. In my 32 bit instalation of Arch, Bijiben crashes when you click the "New" button. On my 64 bits instalation of Arch it works very well. The terminal output is "Segmentation Fault." And no aditional info. I thought it was a distro issue. But talking with some user, they said that same happends in 32 bits instalations of their distros. (Is my second bug filed in upstream so excuse me if there are something wrong or missing.)
Same issue on opensuse tumbleweed x32
*** Bug 697922 has been marked as a duplicate of this bug. ***
you were 39 seconds faster ;) but yeah: i can confirm this on arch32 too ( see the above duplicate bug report )
oops. I'll look at this, eventually running gdb with a break on bjb_controller_add_note might precise the issue but anyway i will check Confirming since it impacts several users.
@Pierre: how do i run that ? im a gdb newbie i attached a backtrace in my original report what should i do more, i realy want to help
yes i checked the backtrace. Once gdb bijiben, you might (gdb) b bjb_controller_add_note (gdb) run when the program pauses (eg if you click on "next"), repeat (gdb) next untill program works or crashes. it might provide a bit more information.
(gdb) b bjb_controller_add_note Function "bjb_controller_add_note" not defined. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 1 (bjb_controller_add_note) pending. (gdb) run Starting program: /usr/bin/bijiben warning: Could not load shared library symbols for linux-gate.so.1. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0xb0969b40 (LWP 5788)] [New Thread 0xaffffb40 (LWP 5789)] [New Thread 0xae783b40 (LWP 5790)] Program received signal SIGSEGV, Segmentation fault. 0xb56a8802 in __strlen_sse2_bsf () from /usr/lib/libc.so.6 (gdb) next Single stepping until exit from function __strlen_sse2_bsf, which has no line number information. [Thread 0xaffffb40 (LWP 5789) exited] [Thread 0xae783b40 (LWP 5790) exited] [Thread 0xb0983880 (LWP 5784) exited] Program terminated with signal SIGSEGV, Segmentation fault. The program no longer exists.
If it helps, here's my debug out: http://paste.opensuse.org/98134796
Well I'd try it on gdb and it said this: Program received signal SIGSEGV, Segmentation fault. 0xb569c802 in __strlen_sse2_bsf () from /usr/lib/libc.so.6 And this is the backtrace. I hope this were useful If it doesn't tell if I cloud do another thing. (gdb) backtrace
+ Trace 231780
Thanks all for these info, indeed this was bjb_controller_add_note, I messed up a glong with a gint64, thus it crashed only on 32 bit. commit 10b444980f0447358371fdcc2707f310a351d020
(In reply to comment #10) > Thanks all for these info, indeed this was bjb_controller_add_note, I messed up > a glong with a gint64, thus it crashed only on 32 bit. > > commit 10b444980f0447358371fdcc2707f310a351d020 Thank you! You did a Great job with app!
Bijiben 3.8.1 still crashes with segmentation fault on x32. Was the fix applied to the 3.8.1 branch?
Ack the fix is missing there, you're right. I've just cherry-picked to correct things. commit 0a7797839330b2b5bacc0f73d084539f4a4c6d04 commit 65f68cf5d048de971d47bacedfc47a01c8b502ca If the package can be patched these two commits would make it. Until 3.8.2
It looks like we'll have to wait another month before we can use your awesomely designed app :(