[Pkg-qof-maintainers] Bug#479374: [gpe-expenses] backtrace and valgrind result

[lidaobing at gmail.com]

Hello,

It also crash if I create two records and edit the second record.



On 5/4/08, Neil Williams <codehelp at debian.org> wrote:
> reassign 479374 libqof1
> tag 479374 + confirmed
> quit
>
> On Sun, 2008-05-04 at 22:13 +0800, LI Daobing
> =?UTF-8?Q?(=E6=9D=8E=E9=81=93=E5=85=B5) ?= wrote:
> > Package: gpe-expenses
> > Version: 0.1.5-1
> >
> > --- Please enter the report below this line. ---
> > backtrace from gdb in [1], valgrind log in attchment.
> >
> > #28 0x00002af73ccad657 in g_main_loop_run () from
> /usr/lib/libglib-2.0.so.0
> > #29 0x00002af73c5f7b63 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
> > #30 0x0000000000407eba in gpe_gui_start (argc=2, argv=0x7fff6ee83178,
> > context=0x618590) at gpe-expenses.c:141
> > #31 0x00000000004088d8 in main (argc=2, argv=0x7fff6ee83178) at
> > gpe-expenses.c:331
>
> You would get more useful output if you installed the -dbg package(s)
> but I have worked out where this bug occurs and I've got a fix that I
> will continue testing. (I expect it arose when you were testing the new
> translation files from the other bugs - sorry about that.)
>
> The problem isn't in gpe-expenses, it is in the QOF library which should
> have returned a newly allocated empty string instead of a NULL.
> (qofutil.c: 511)
>
> Can you confirm that once you create the first expense, that the
> application operates as normal from then on, or does it recur if you
> create a second expense?
>
> --
>
>
> Neil Williams
> =============
> http://www.data-freedom.org/
> http://www.nosoftwarepatents.com/
> http://www.linux.codehelp.co.uk/
>
>
>


-- 
Best Regards,
 LI Daobing