[sword-devel] Xiphos crashes with my sword locale
Hello, Somebody have an idea why Xiphos crashes with the my-utf8.conf file when I try to move to some books with this error: |(process:7859): Gtk-WARNING **: 23:53:31.125: Locale not supported by C library. Using the fallback 'C' locale. (xiphos:7849): Gdk-CRITICAL **: 23:53:33.023: gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed *** buffer overflow detected ***: xiphos terminated | This seems to happen with longer names. I don't have this problem with Bibletime. || ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
[sword-devel] Xiphos crashes with my sword locale
Hello, Somebody have an idea why Xiphos crashes with the my-utf8.conf file when I try to move to some books with this error: |(process:7859): Gtk-WARNING **: 23:53:31.125: Locale not supported by C library. Using the fallback 'C' locale. (xiphos:7849): Gdk-CRITICAL **: 23:53:33.023: gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed *** buffer overflow detected ***: xiphos terminated | This seems to happen with longer names. I don't have this problem with Bibletime. || ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Xiphos crashes with my sword locale
On 11/5/19 9:09 AM, Cyrille wrote: |*** buffer overflow detected ***: xiphos terminated| It would help if you could run it under gdb to get a backtrace for what function/line is the choke point. ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Xiphos crashes with my sword locale
Le 05/11/2019 à 10:18, Karl Kleinpaste a écrit : > On 11/5/19 9:09 AM, Cyrille wrote: >> |*** buffer overflow detected ***: xiphos terminated| > It would help if you could run it under gdb to get a backtrace for > what function/line is the choke point. I'm ready to do everything! But I don't know what means gdb. Let me know how to do. > > ___ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Xiphos crashes with my sword locale
On 11/5/19 10:20 AM, Cyrille wrote: But I don't know what means gdb. Let me know how to do. http://ftp.xiphos.org/sword/debugging/backtrace ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Xiphos crashes with my sword locale
Le 05/11/2019 à 10:22, Karl Kleinpaste a écrit : > On 11/5/19 10:20 AM, Cyrille wrote: >> But I don't know what means gdb. Let me know how to do. > http://ftp.xiphos.org/sword/debugging/backtrace Thread 1 "xiphos" received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 51 ../sysdeps/unix/sysv/linux/raise.c: Aucun fichier ou dossier de ce type. (gdb) bt #0 0x71eace97 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x71eae801 in __GI_abort () at abort.c:79 #2 0x71ef7897 in __libc_message (action=action@entry=(do_abort | do_backtrace), fmt=fmt@entry=0x72024988 "*** %s ***: %s terminated\n") at ../sysdeps/posix/libc_fatal.c:181 #3 0x71fa2cff in __GI___fortify_fail_abort (need_backtrace=need_backtrace@entry=true, msg=msg@entry=0x72024905 "buffer overflow detected") at fortify_fail.c:33 #4 0x71fa2d21 in __GI___fortify_fail (msg=msg@entry=0x72024905 "buffer overflow detected") at fortify_fail.c:44 #5 0x71fa0a10 in __GI___chk_fail () at chk_fail.c:28 #6 0x71f9fca2 in __strcpy_chk (dest=0x57492190 "", src=0x566bed50 "ထွက်မြောက်ရာကျမ်း 1:1", destlen=50) at strcpy_chk.c:30 #7 0x555ecee7 in main_add_tab_history_item () #8 0x555a5768 in () #9 0x555e7c82 in main_display_bible () #10 0x555ed869 in () #11 0x555edc8f in main_url_handler () #12 0x555966d1 in () #13 0x7776310d in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ---Type to continue, or q to quit--- I'll post it on the github issue. > > ___ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Xiphos crashes with my sword locale
On 11/5/19 10:31 AM, Cyrille wrote: #6 0x71f9fca2 in __strcpy_chk (dest=0x57492190 "", src=0x566bed50 "ထွက်မြောက်ရာကျမ်း 1:1", destlen=50) at strcpy_chk.c:30 Bug found. A fix will happen for next release. That won't be today or next week, but ... I'm thinking Christmas or thereabouts. For now... well, you're stuck, because the problem is that the space occupied by that book name is 51 bytes. (Somehow it figures.) You can blame either Terry or me for that arbitrarily short limit, probably a decade and a half ago. In fact, in a fit of unclean code, that limit of 50 is imposed on both the length of names in a history event as well as the number of history events, when it should have been only the latter. ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Xiphos crashes with my sword locale
Le 05/11/2019 à 11:01, Karl Kleinpaste a écrit : > On 11/5/19 10:31 AM, Cyrille wrote: >> #6 0x71f9fca2 in __strcpy_chk (dest=0x57492190 "", >> src=0x566bed50 "ထွက်မြောက်ရာကျမ်း 1:1", destlen=50) >> at strcpy_chk.c:30 > Bug found. A fix will happen for next release. That won't be today or > next week, but ... I'm thinking Christmas or thereabouts. For now... > well, you're stuck, because the problem is that the space occupied by > that book name is 51 bytes. (Somehow it figures.) You can blame either > Terry or me for that arbitrarily short limit, probably a decade and a > half ago. In fact, in a fit of unclean code, that limit of 50 is > imposed on both the length of names in a history event as well as the > number of history events, when it should have been only the latter. Thank you Karl! For Christmas it will be a nice gift for my friend in Myanmar. The locale my-utf8.conf is not yet released. I just patch it in the sword package of my ubuntu ppa. But I don't have it for Windows. Then if you'll propose a new exe for Windows I can share with you the file. You have also a new pull request on github for this local. The last question is, what is the "correct" locale, my, bm or my_MY? I used my, it works but I want to be sure. ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
