After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 393817 - Add Report Button crashes Gnucash (Mac OSX)
Add Report Button crashes Gnucash (Mac OSX)
Status: VERIFIED DUPLICATE of bug 543063
Product: GnuCash
Classification: Other
Component: Reports
2.0.x
Other Mac OS
: Normal critical
: ---
Assigned To: Chris Lyttle
Chris Lyttle
Depends on:
Blocks:
 
 
Reported: 2007-01-07 07:39 UTC by David
Modified: 2018-06-29 21:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gnucash.trace (1.18 KB, application/octet-stream)
2007-01-09 23:23 UTC, David
Details

Description David 2007-01-07 07:39:02 UTC
Steps to reproduce:
1. Open a report
2. Customize it (using a new name)
3. Click Add Report button


Stack trace:


Other information:
Report gets added, but GnuCash crashes out. Mac OS X (Intel)
Comment 1 Christian Stimming 2007-01-08 10:16:36 UTC
I think this has been fixed in 2.0.2 or later. Can you please update and check again?
Comment 2 David 2007-01-09 08:41:10 UTC
Updated to 2.0.4. Still happens. saved-reports-2.0 gets report info, GnuCash disappears.
Comment 3 Christian Stimming 2007-01-09 09:13:15 UTC
Oh, thanks for the info. We haven't been able to reproduce this crash ourselves so far, so we'd like to ask for some more information: 
* If you start gnucash from a command line, does it show any messages on the command line when it crashes?
* Can you attach the content of the file /tmp/gnucash.trace here? ("add attachment" below)
* Can you try to get a stack trace http://wiki.gnucash.org/wiki/Stack_Trace and attach it here?
Thanks a lot.
Comment 4 David 2007-01-09 23:23:23 UTC
Created attachment 79904 [details]
gnucash.trace
Comment 5 David 2007-01-09 23:29:19 UTC
Answers:

1) No command line messages on crash

2) Attached my gnucash.trace (79904)

3) I followed the Wiki. The text is included below (note the No Stack error at the end):

macbook:~ david$ gdb
GNU gdb 6.1-20040303 (Apple version gdb-437) (Fri Jan 13 18:45:48 GMT 2006)
Copyright 2004 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-apple-darwin".
(gdb) attach 17115
Attaching to process 17115.
Reading symbols for shared libraries . done
Reading symbols for shared libraries ...........................................
................................................................................
................................................... done
0x90019d3c in select ()
(gdb) continue
Continuing.
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done

Program exited with code 02.
You can't do that when your target is `None'
You can't do that when your target is `None'
(gdb) backtrace
No stack.
Comment 6 Christian Stimming 2007-01-10 21:00:11 UTC
Errr... thanks for the info. Unfortunately, in none of the places any actual information about the crash is shown: no scheme backtrace on the console, no C backtrace in gdb, no crash information in gnucash.trace. The last resort would be to manually add scheme debugging output to the function in question, but that has to be done probably by a scheme/lisp expert who has access to a Mac OSX machine. 

For the record: The function in question is in src/report/report-system/report.scm gnc:report-save-to-savefile; maybe the (force-output) is a problem for the Mac. I'd think I'd add a (display "here") before and after the (force-output) function call...
Comment 7 Rolf Leggewie 2008-07-10 09:30:00 UTC
still a problem with the most recent 2.2.x version?
Comment 8 Christian Stimming 2008-10-29 21:28:30 UTC

*** This bug has been marked as a duplicate of 543063 ***
Comment 9 John Ralls 2018-06-29 21:21:41 UTC
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=393817. Please update any external references or bookmarks.