segfaults in gnc-html-guppi.c

[Dave Peticolas]

--=-wF6llWETp1RRsZ3IQsVq
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Fri, 2001-08-24 at 16:20, Christian Stimming wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
>=20
> I was debugging the [xy]-axis labels of the Guppi barcharts. While I trie=
d=20
> those, I encountered mysterious segfaults caused from gnc-html-guppi.c. T=
hose=20
> seemed to appear after too many subsequent calls to g_hash_table_lookup w=
ith=20
> negative result. GDB said this:
>
> Program received signal SIGSEGV, Segmentation fault.
> #0  0x400eb10b in g_hash_table_lookup () from /usr/lib/libglib-1.2.so.0
> #1  0x80d21b7 in gnc_html_embedded_barchart (parent=3D0x1, w=3D400, h=3D4=
00,
>     params=3D0x4) at gnc-html-guppi.c:784
> #2  0x8132a46 in gnc_account_tree_info.118 ()
> Cannot access memory at address 0x4
>=20
>=20
> Note the GDB message's line number gnc-html-guppi.c:784 (or as well 785):=
=20
> This is the 19th call (of 20) of g_hash_table_lookup in a row. If the #de=
fine=20
> is set to false, you will have 16 of them, and if your Guppi is 0.35.5 or=
=20
> small you will still have a maximum of 18 of those calls. Hence, this err=
or=20
> won't occur unless you have things set up in the described way.
>=20
> Can anybody reproduce that? Can anyone get more information out of his=20
> debugger?

I don't have the latest guppi, but I notice that the html-barchart.scm
doesn't seem to set the normalize_stacks argument. Could that be the
source of the problem?

dave


--=-wF6llWETp1RRsZ3IQsVq
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQA7ifRu5effKKCmfpIRAoxuAKCwIiPPKXANUYn79DH46mYJ7ia0zQCg2Ax0
Ycnccjz9FGkVh0v/lEGQFvI=
=3leH
-----END PGP SIGNATURE-----

--=-wF6llWETp1RRsZ3IQsVq--