Payable Aging Report Totals column produces error

[Gene]

Charles Day wrote:
> On Tue, Jun 10, 2008 at 9:17 AM, Charles Day <cedayiv at gmail.com 
> <mailto:cedayiv at gmail.com>> wrote:
>
>     On Tue, Jun 10, 2008 at 6:46 AM, Derek Atkins <warlord at mit.edu
>     <mailto:warlord at mit.edu>> wrote:
>
>         Hi,
>
>         Gene <genestairs at gmail.com <mailto:genestairs at gmail.com>> writes:
>
>         > Well, I installed the desktop full version of 2.25 and
>         received the
>         > same error.
>         > This did generate a gnucash.trace file, and here's the contents,
>         > however I have no idea what it means....
>         >
>         > *   WARN <qof.engine> [guid_init()] only got 2441 bytes.
>         > The identifiers might not be very random.
>         > *   WARN <gnc.app-util> Could not spawn perl: Failed to
>         execute child
>         > process (No such file or directory)
>         > *   WARN <Gdk> gdkselection-win32.c:1068: OpenClipboard failed:
>         > Invalid window handle.
>         > *   WARN <Gdk> gdkselection-win32.c:1068: OpenClipboard failed:
>         > Invalid window handle.
>
>         Unfortunately it means absolutely nothing.
>
>         If the report actually had an ERROR it should have printed it out
>         to the trace file...   Or the console.  But there is no console
>         on win32 so anything printed _there_ gets lost.
>
>
>     The error is probably happening in the report's Scheme code. If
>     you could see console output, there would be a nice set of
>     debugging messages that would really help.
>
>     I wonder if the result would be any different if you launched
>     GnuCash from a DOS-style command prompt, rather than from an icon.
>
>     Derek, when I get a second I'll see if I can figure out a way to
>     get Scheme backtraces directed to gnucash.trace instead of (or in
>     addition to) the console. That sure would help sometimes.
>
>
> Committed as r17209 with backport requested.
>
> Gene, if you want to try out this patch, it should get the Scheme 
> debugging output into the trace file where you can see it.
>
> -Charles
Can you give me quick directions how to apply this?
Do I need to cut and paste into a file, and then run?

>
> $ svn diff src/scm/main.scm
> Index: src/scm/main.scm
> ===================================================================
> --- src/scm/main.scm    (revision 17208)
> +++ src/scm/main.scm    (working copy)
> @@ -130,8 +130,18 @@
>  (define (gnc:backtrace-if-exception proc . args)
>    (define (dumper key . args)
>      (let ((stack (make-stack #t dumper)))
> +      ;; Send debugging output to the console.
>        (display-backtrace stack (current-error-port))
>        (apply display-error stack (current-error-port) args)
> +
> +      ;; Send debugging output to the log.
> +      (if (defined? 'gnc:warn)
> +          (let ((string-port (open-output-string)))
> +            (display-backtrace stack string-port)
> +            (apply display-error stack string-port args)
> +            (gnc:warn (get-output-string string-port))
> +            (close-output-port string-port)))
> +
>        (throw 'ignore)))
>   
>    (catch
>