> Dave Peticolas writes:
>
> > Does anyone know the right way to print a backtrace
> > in 1.3.4? The way it's currently being done is in the
> > function gnc:error->string in c-interface.scm.
>
> You could try mailing the guile-list, which is hosted (and archived)
> at sourceware.cygnus.com
Dave Peticolas writes:
> Does anyone know the right way to print a backtrace
> in 1.3.4? The way it's currently being done is in the
> function gnc:error->string in c-interface.scm.
You could try mailing the guile-list, which is hosted (and archived)
at sourceware.cygnus.com
> >
> > Does anyone know the right way to print a backtrace
> > in 1.3.4? The way it's currently being done is in the
> > function gnc:error->string in c-interface.scm.
> >
>
> Dave, where's the documentation for display-backtrace? I can't find
> it in the guile info documentation.
>
>
Dave Peticolas writes:
> > Dave Peticolas writes:
> > > > Dave Peticolas writes:
> > > >
> > > > > > Is there anything I need to do to enable backtraces?
> > > > >
> > > > > It's supposed to work no matter what, but just as a test
> > > > > you might try running gnucash with the
> Dave Peticolas writes:
> > > Dave Peticolas writes:
> > >
> > > > > Is there anything I need to do to enable backtraces?
> > > >
> > > > It's supposed to work no matter what, but just as a test
> > > > you might try running gnucash with the --debug argument.
> > > >
> > > Nope, d
> As promised, I'm currently working on adding periodicity to
> the balance and profit-and-loss reports.
>
> Not surprisingly, I've made a few mistakes along the way, and
> was expecting the stack backtrace to make my life easier.
>
> Unfortunately, while the actual error is recorded, I'm not
>
As promised, I'm currently working on adding periodicity to
the balance and profit-and-loss reports.
Not surprisingly, I've made a few mistakes along the way, and
was expecting the stack backtrace to make my life easier.
Unfortunately, while the actual error is recorded, I'm not
seeing a backtr
