[Sks-devel] Dump recurses to dumpsize on stack?

[Phil Pennock]

Is it known that when you do "sks dump <N> <dir>", you end up with up to
10 stack frames per N, plus the calls into the DB layer, etc?

There's nothing in TODO about this, so I'm guessing not.

#26012 0x0000000803aabbc8 in ?? ()
#26013 0x0000000800f3c5d8 in ?? ()
#26014 0x00000000000188c3 in ?? ()
#26015 0x0000000800f5ee60 in ?? ()
#26016 0x0000000800f53ac8 in ?? ()
#26017 0x0000000800f5e1f0 in ?? ()
#26018 0x000000000000091f in ?? ()
#26019 0x0000000000412a9d in camlSksdump__write_to_file_727 ()
#26020 0x00007fffffc33170 in ?? ()
#26021 0x00000000004128d3 in camlSksdump__write_to_file_727 ()

FreeBSD/amd64, single-core system.

I was suspecting db problems, and it's not.  Looks as though something
was expecting tail recursion optimisation but not getting it.  I really
don't know enough about programming in functional languages to look into
this properly.  I don't even know if things like shuffling exception
handling around would let the tail recursion optimisation kick in and
where things like integrity of backup dumps are concerned, I play around
less.

Yaron?  Kim?

-Phil

pgpKwjJCs4bh4.pgp
Description: PGP signature