Can you build a debug version of Ledger and try it again? This is what you will get if you just run 'acprep update'.
If you want to keep multiple build variants around, just make a 'build' directory in the Ledger source tree before running acprep. You'll then find build/debug/ledger. John On Nov 23, 2009, at 5:32 PM, Simon Michael wrote: > My recent master build segfaults if I run register with an account pattern. > Here's the backtrace (doesn't seem too helpful though.) > > > (gdb) run -f ~/src/hledger/sample.ledger reg assets > run -f ~/src/hledger/sample.ledger reg assets > Starting program: /Users/simon/src/ledger/ledger -f > ~/src/hledger/sample.ledger reg assets > Reading symbols for shared libraries . done > Reading symbols for shared libraries +++++++++++++++++....warning: Could not > find object file > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_re$ > > warning: Could not find object file > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_archivers_bzip2/work/bzip2-1.0.5/huffman.o" > - $ > > warning: Could not find object file > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_archivers_bzip2/work/bzip2-1.0.5/crctable.o" > -$ > > warning: Could not find object file > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_archivers_bzip2/work/bzip2-1.0.5/randtable.o" > $ > > warning: Could not find object file > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_archivers_bzip2/work/bzip2-1.0.5/compress.o" > -$ > > warning: Could not find object file > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_archivers_bzip2/work/bzip2-1.0.5/decompress.o"$ > > warning: Could not find object file > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_archivers_bzip2/work/bzip2-1.0.5/bzlib.o" > - no$ > > .. done > > Program received signal EXC_BAD_ACCESS, Could not access memory. > Reason: KERN_INVALID_ADDRESS at address: 0x02fffffc > 0xffff0f1a in ?? () > (gdb) bt > bt > #0 0xffff0f1a in ?? () > #1 0x0280c810 in ?? () > Previous frame inner to this frame (gdb could not unwind past this frame) >
