Segmentation Fault in xaccFreeSplit

Derek Atkins warlord at MIT.EDU
Fri Jan 21 23:10:37 EST 2005

Quoting Matthew Vanecek <mevanecek at>:

> I'm kinda skeptical about using the contents of a freed Split to see if
> the Split has been freed, though.  What if something else has
> overwritten the freed memory?  Why is that particular pointer guaranteed
> to still be == (char *)1 if the split is run through the function again?

It's not.  The data could be completely bogus.  It's just a debugging tool.


       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL:    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available

More information about the gnucash-devel mailing list