GNOME Bugzilla – Bug 107006
Scheduled Transaction SEGV
Last modified: 2018-06-29 20:29:16 UTC
I'm getting a reocurring crash while using the Scheduled Transaction Editor. I get the crash under the Red Hat 8.1 beta with GnuCash 1.8.1 and also under Red Hat 8.0 with the GnuCash RPMs from the GnuCash site. Here is the backtrace: Script started on Thu 13 Feb 2003 09:26:18 PM EST neuromancer> gnucash-env gdb /usr/bin/guile GNU gdb Red Hat Linux (5.3post-0.20021129.11rh) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"... (no debugging symbols found)... (gdb) run -e main -s /usr/libexec/gnucash/overrides/gnucash Starting program: /usr/bin/guile -e main -s /usr/libexec/gnucash/overrides/gnucash (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 1075008160 (LWP 6618)] Program received signal SIGINT, Interrupt.
+ Trace 34243
Thread 1075008160 (LWP 6618)
(gdb) quit The program is running. Exit anyway? (y or n) y neuromancer> exit Script done on Thu 13 Feb 2003 09:27:39 PM EST
Created attachment 14594 [details] Gzip'ed typescipt of an strace of the same type of crash
Here is another backtrace of another crash when trying to open the Scheduled Transaction Editor: Script started on Sun 16 Feb 2003 08:31:14 PM EST neuromancer> gnucash-env gdb /usr/bin/guile GNU gdb Red Hat Linux (5.3post-0.20021129.12rh) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"... (no debugging symbols found)... (gdb) run -e main -s /usr/libexec/gnucash/overrides/gnucash Starting program: /usr/bin/guile -e main -s /usr/libexec/gnucash/overrides/gnucash (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 1075008160 (LWP 6937)] Program received signal SIGINT, Interrupt.
+ Trace 34244
Thread 1075008160 (LWP 6937)
(gdb) quit The program is running. Exit anyway? (y or n) y neuromancer> exit Script done on Sun 16 Feb 2003 08:33:40 PM EST
Appears to be a unique stack trace, according to the simple-dup-finder. Marking priority->high & severity->critical (it's a crasher), adding bugsquad keyword, and marking as new.
Here are three more gdb runs on a Red Hat 8.0 system using the 1.8.2 rpms from the gnucash site. I start gnucash, immediately go to the scheduled transaction editor, and then edit transactions until it dies. The first run allowed me to actually edit a transaction before it crashed while the second two crashed after the editor window appeared but before anything was drawn in it. wintermute> cat typescript Script started on Tue Mar 11 08:18:00 2003 wintermute> gnucash-env gdb /usr/bin/guile GNU gdb Red Hat Linux (5.2.1-4) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux"... (no debugging symbols found)... (gdb) run -e main -s /usr/libexec/gnucash/overrides/gnucash Starting program: /usr/bin/guile -e main -s /usr/libexec/gnucash/overrides/gnucash [New Thread 8192 (LWP 8567)] ** CRITICAL **: file gnc-transaction-xml-v2.c: line 443 (set_tran_date): assertion `tm' failed. ** CRITICAL **: file gnc-transaction-xml-v2.c: line 443 (set_tran_date): assertion `tm' failed. ** CRITICAL **: file gnc-transaction-xml-v2.c: line 443 (set_tran_date): assertion `tm' failed. ** CRITICAL **: file gnc-transaction-xml-v2.c: line 443 (set_tran_date): assertion `tm' failed. ** CRITICAL **: file gnc-transaction-xml-v2.c: line 443 (set_tran_date): assertion `tm' failed. ** CRITICAL **: file gnc-transaction-xml-v2.c: line 443 (set_tran_date): assertion `tm' failed. ** CRITICAL **: file gnc-transaction-xml-v2.c: line 443 (set_tran_date): assertion `tm' failed. ** CRITICAL **: file gnc-transaction-xml-v2.c: line 443 (set_tran_date): assertion `tm' failed. Transactions: Total: 193, Loaded: 201 Accounts: Total: 122, Loaded: 121 Books: Total: 1, Loaded: 0 Commodities: Total: 4, Loaded: 4 Scheduled Tansactions: Total: 8, Loaded: 6 Transactions: Total: 193, Loaded: 201 Accounts: Total: 122, Loaded: 121 Books: Total: 1, Loaded: 0 Commodities: Total: 4, Loaded: 4 Scheduled Tansactions: Total: 8, Loaded: 7 Transactions: Total: 193, Loaded: 201 Accounts: Total: 122, Loaded: 121 Books: Total: 1, Loaded: 0 Commodities: Total: 4, Loaded: 4 Scheduled Tansactions: Total: 8, Loaded: 8 ** CRITICAL **: file gnc-component-manager.c: line 271 (gnc_cm_event_handler): assertion `id_type' failed. Program received signal SIGSEGV, Segmentation fault.
+ Trace 34759
Thread 8192 (LWP 8567)
Thread 8192 (LWP 8632)
Thread 8192 (LWP 8702)
(gdb) quit The program is running. Exit anyway? (y or n) yes wintermute> exit exit Script done on Tue Mar 11 08:30:32 2003 wintermute>
I'm doing some tidying on gnucash bugs. Can you tell me if this bug still exists in the latest gnucash (1.8.5 or even 1.8.4)?
Yes. It still hangs for me, or crashes guile, while doing scheduled transaction editing. I'm using 1.8.5.
Hmm, you still running RH8.0? What kernel version (send me the uuname -a output). Unfortunately I can't duplicate this because I'm on RH9. I abandoned RH8 due to general instability problems. There were some serious thread issues in RH8 which (in my case) caused hangs. I know its asking a lot, but any chance of upgrading to RH9? We just aren't seeing anybody else with this sort of massive problem. Any information about your environment would be useful, but unless I can duplicate the crash I'm a little at sea.
I am running RH9. In fact, I'm running rawhide. The bug has followed me from RH8 to RH9 to rawhide. But I was able to duplicate the bug under Debian SID as well.
OK, if you are getting it on RH9 then I can have a go at duplicating it. Do you have an .xac file that I can try? Also, a look at your .gnucash directory tree would be helpful. Also what LOCALE are you using? Obviously, any personal data that you give me would be kept in strictest confidence.
Don't have any LOCALE set: neuromancer> printenv USER=tjb LOGNAME=tjb HOME=/home/tjb PATH=/home/tjb/bin:/usr/local/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/etc:/usr/games:/usr/sbin:/sbin:/opt/bin:/usr/local/sbin MAIL=/var/mail/tjb SHELL=/bin/tcsh SSH_CLIENT=10.0.1.1 52311 22 SSH_CONNECTION=10.0.1.1 52311 10.0.1.100 22 SSH_TTY=/dev/pts/0 TERM=vt100 DISPLAY=localhost:10.0 SSH_AUTH_SOCK=/tmp/ssh-jInV7306/agent.7306 HOSTTYPE=i386-linux VENDOR=intel OSTYPE=linux MACHTYPE=i386 SHLVL=1 PWD=/home/tjb GROUP=bc HOST=neuromancer.bakerconsulting.com REMOTEHOST=bakerconsulting.com LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=01;32:*.cmd=01;32:*.exe=01;32:*.com=01;32:*.btm=01;32:*.bat=01;32:*.sh=01;32:*.csh=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*.tif=01;35: G_BROKEN_FILENAMES=1 SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass LANG=en_US.UTF-8 SUPPORTED=en_US.UTF-8:en_US:en LESSOPEN=|/usr/bin/lesspipe.sh %s LANGVAR=en_US.UTF-8 QTDIR=/usr/lib/qt-3.1 HOSTNAME=neuromancer.bakerconsulting.com PILOTPORT=/dev/pilot PILOTRATE=115200 EVOLVE_ME_HARDER=nosplashthanks SANE_NET_HOSTS=millennium GDK_USE_XFT=1 SSH_AGENT_PID=7308 neuromancer> Not much in .gnucash: neuromancer> ls -lR .gnucash .gnucash: total 12 drwx------ 2 tjb bc 4096 Sep 5 08:44 books/ -rw-r--r-- 1 tjb bc 6312 Sep 5 08:50 config-1.8.auto .gnucash/books: total 4 -rw-r--r-- 1 tjb bc 1119 Sep 5 08:50 %2Fhome%2Ftjb%2FFinances%2FFinances neuromancer> Do you want me to tar it up for you? I'll work on the .xac file.
Yes please, tar up the .gnucash directory and I'll see if it is something in your setup, I'll await your .xac file.
Created attachment 19841 [details] Gzipped tar of .gnucash directory
Apologies for the delay on this. I somehow missed the posting of the example file. I'm very busy at the present, but will try and spend some time on it over Christmas.
This is definitely the weekly memory corruption issue. Dup. *** This bug has been marked as a duplicate of 125600 ***
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=107006. Please update any external references or bookmarks.