Unit test failure #346

Closed
ghost opened this Issue Jan 15, 2014 · 6 comments

1 participant

@ghost

At least one unit test failed:

TEST: test-mu-store... (pid=76605)
/mu-store/mu-store-new-destroy: test-mu-store(76605) malloc: *** error for object 0x7fff75121860: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
FAIL
GTester: last random seed: R02S7e3da0dff3e21cbdf14c4e1

This same failure happens at runtime when running mu from the command line:

mu(76684) malloc: *** error for object 0x7fff75121860: pointer being freed was not allocated

Here is the version of mu:
mu (mail indexer/searcher) version 0.9.9.6pre2

I am on a Macbook Pro with OS X Lion.

@ghost

I see that you posted a commit an hour ago that looks aimed at fixing this error. I blew away the old repo, cloned a new one and ran make check again. Same error:

TEST: test-mu-store... (pid=9838)
/mu-store/mu-store-new-destroy: test-mu-store(9838) malloc: *** error for object 0x7fff75121860: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
FAIL
GTester: last random seed: R02S5ab61143c83cfa84996b430b6ff2264b
/bin/sh: line 1: 9820 Terminated: 15 gtester --verbose test-mu-util test-mu-str test-mu-maildir test-mu-msg-fields test-mu-msg test-mu-store test-mu-date test-mu-flags
make[2]: *** [test] Error 143
make[1]: *** [test] Error 2
make: *** [test] Error 2

Could it be something in my environment?

@djcb
Owner

Yeah, I tried the unit test but it didn't work for me (for a different reason, I think something changed in some lib).
I fixed that, and now the tests works again for me.

Are you on BSD or MacOS by any chance? And can you provide a backtrace? Thanks!

@ghost

I'm on OS X Lion. I included the backtrace in the first and second comments. If there is more I can provide, then I am more than happy too.

@ghost

Here is the backtrace again, along with the command:

$ mu index
mu(10167) malloc: *** error for object 0x7fff75121860: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
[1] 10167 abort mu index

@ghost

I was able to get a working mu by uninstalling the latest source build and using homebrew to install mu 0.9.9.5. I also did a git checkout v0.9.9.5 to get a mu4e that I should work with mu 0.9.9.5. It does, with a one bug (hot keys in the mu4e UI are all * instead of j, U, bu, etc.), but that is just a visual issue which doesn't affect use.

@djcb
Owner

Is this still reproducible?

@djcb djcb closed this Nov 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment