Bug 97522 - gnucash crashing repeatedly using postgres backend
Summary: gnucash crashing repeatedly using postgres backend
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: gnucash
Version: 1.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-06-17 06:00 UTC by Jonathan Kamens
Modified: 2014-03-17 02:36 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-01-28 22:21:23 UTC
Embargoed:


Attachments (Terms of Use)

Description Jonathan Kamens 2003-06-17 06:00:51 UTC
When attempting to save data into the postgres backend with gnucash, it's
segfaulting on me pretty regularly in /usr/bin/guile.  For example, once all I
did was created a new file with "Common Accounts" and then save it as
postgres://localhost/accounts and I got a segfault.  Unfortunately it doesn't
seem to be leaving a coredump anywhere.  I've got guile-1.6.4-6.2,
gnucash-1.8.4-1, and postgresql-7.3.3-3.

Comment 1 Bill Nottingham 2003-06-17 06:04:42 UTC
ulimit -c unlimited may help with core dumps.

If you install the gnucash-debuginfo at http://people.redhat.com/notting/gnucash/,
do you get a useful backtrace?

Comment 2 Jonathan Kamens 2003-06-20 03:00:13 UTC
Hmm.  I had ulimit -c unlimited in my dotfiles, but it was overridden in the
window that I start with "xterm -ls" because of a competing line in
/etc/profile.  I've fixed that, so I'll get coredumps in that window from now on.

As for the other stuff, I'm afraid I must plead "no time to debug."  I already
spent one all-nighter converting from cbb to GnuCash; I can't afford another one
for a while :-).


Comment 3 Bill Nottingham 2005-01-28 22:21:23 UTC
Closing bugs from older, end-of-life releases. Apologies for any lack of response.

Please attempt to reproduce problems on a current distro, such as Fedora Core 3.



Note You need to log in before you can comment on or make changes to this bug.