Re: Segfault on next branch

2012-03-10 Thread John Wiegley
Hyrum K Wright hyrum-krattusis2oizk9zyxr...@public.gmane.org writes: Everything was working just fine until I added a single entry. Running on just that entry doesn't give any problems, and I've yet to find a small reproduction recipe. However, the above problem is reproducible for me on

Segfault on next branch

2012-03-01 Thread Hyrum K Wright
Running the following command on the next branch results in a segfault: $ ./ledger -s bal Checking The backtrace from gdb is: Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x 0x0001000f8720 in ledger::(anonymous

Re: Segfault on next branch

2012-03-01 Thread John Wiegley
Hyrum K Wright hyrum-krattusis2oizk9zyxr...@public.gmane.org writes: Running the following command on the next branch results in a segfault: $ ./ledger -s bal Checking See if what's on 'next' now fixes your problem. John

Re: Segfault on next branch

2012-03-01 Thread Hyrum K Wright
On Thu, Mar 1, 2012 at 9:19 PM, John Wiegley jwieg...@gmail.com wrote: Hyrum K Wright hyrum-krattusis2oizk9zyxr...@public.gmane.org writes: Running the following command on the next branch results in a segfault:   $ ./ledger -s bal Checking See if what's on 'next' now fixes your problem.