segfaults when running graphical reports

[John Ralls]

On Apr 13, 2014, at 8:41 AM, Thomas Klausner <tk at giga.or.at> wrote:

> Hi John!
> 
> On Sun, Apr 13, 2014 at 08:18:17AM -0700, John Ralls wrote:
>> 
>> On Apr 13, 2014, at 12:35 AM, Thomas Klausner <tk at giga.or.at> wrote:
>> 
>>> Hi!
>>> 
>>> I'm using gnucash-2.6.3 from pkgsrc on NetBSD-6.99.40/amd64.
>>> 
>>> I see two recent changes compared to 2.4.13, the previous version in
>>> pkgsrc.
>>> 
>>> The first: If I start gnucash without a terminal or in the background,
>>> it doesn't finish startup. When started in the background, I see (with
>>> zsh):
>>> 
>>>> gnucash &
>>> [1] 7303
>>>> 
>>> [1]  + suspended (tty output)  gnucash
>>> 
>>> When I put it in the foreground again, it continues starting
>>> successfully. This seems to happen during the splash screen, the last
>>> thing that's displayed in the progress text at the bottom is
>>> "gnucash/python". Perhaps this is a problem with a python module, but
>>> how do I find out which?
>> 
>> The problem is whatever output is going to the terminal. What is it?
>> 
>> Note that you can work around the problem with a redirect: guncash > /dev/null 2>&1 &
> 
> The only thing that's on stdout is "Found Finance::Quote version 1.18"
> and that's been there forever; i.e. this was also there when I still
> could start gnucash in the background. Nothing else is going to the
> terminal (to make sure, I just re-tried with redirecting stdout and
> stderr). Also, usually backgrounding a process doesn't cause issues
> with output, it's just written anyway. For example "cat filename &"
> works fine. So I'm confused why this stops the startup in this case.

Sorry, failed to address this in my other message.

If the terminal output is the same as always, then the easiest way to find out what the problem is is to attach the suspended process in the debugger and get a stack trace.

Regards,
John Ralls