jeckmann writes

newest recollindex crashes using hg pull

(I have a home directory![Screenshot-Untitled Window.png](https://bitbucket.org/repo/LoKMq/images/1222054135-Screenshot-Untitled%20Window.png)

can login without password… (is this the cause?)

medoc writes

Weird !

By "login without a password", do you mean that you actually have no password or that the system creates an automatic session for you when booting ? Anyway, I can’t see how this could be the issue.

Are you using the main branch or the 1.20 maintenance one ?

Can you remember what was the last time you updated your source set before this ?

What system are you running this on ?

Given the stack trace, it seems that malloc should print a message before the crash. What is it ?

jeckmann writes

I am also puzzled.

I just do

cd ~/export/recoll hg pull hg update

(I guess thats the bleeding edge?, I am interested in any improvements, so I use that. The ubuntu distro gives a working older version)

I cannot reconstruct the last date precisely.

But a backup of my computer from march 27 shows the same phenomenon

I also checked a version from Feb 20. same.

Note: At that date I migrated to a new laptop: Ubuntu Mate 14.04

But I know that the program DID work on the new machine. Did Ubuntu mess with a library?

(I also keep that always up-to-date…)

Will let you know if I find anything. (I can of course hard-wire into recollindex my home-directory and see if there are other problems

JPEckmann

  • >--- you can reply above this line ---

  • >

  • >Issue 231: crash

  • >https://bitbucket.org/medoc/recoll/issue/231/crash

  • >

  • >medoc:

  • >

  • >Weird !

  • >

  • >By "login without a password", do you mean that you actually have no password or that the system creates an automatic session for you when booting ?

  • >Anyway, I can’t see how this could be the issue.

  • >

  • >Are you using the main branch or the 1.20 maintenance one ?

  • >

  • >Can you remember what was the last time you updated your source set before this ?

  • >

  • >What system are you running this on ?

  • >

  • >Given the stack trace, it seems that malloc should print a message before the crash. What is it ?

  • >

  • >

  • >

  • >--

  • >

  • >Unwatch this issue to stop receiving email updates:

  • >https://bitbucket.org/api/1.0/medoc/recoll/issue/231/unwatch/jeckmann/b3ef98c9fea090e538b7e5d65103fd795c16b4ad/

  • >

medoc writes

script to remove all installed recoll stuff (does not touch the index data, just executables and others).

medoc writes

When you attach a file, bitbucket erases everything you were typing. great… Here I go again then:

I tried to reproduce this on an up to date 14.04 ubuntu machine, no success. It’s quite unlikely that Ubuntu would introduce a bug in a basic library in an LTS release. What you could try is to remove all recoll bits from the machine using the attached "cleanrecoll" script, then run

#!shell
make clean
configure --prefix=/usr
make
sudo make install

and see if it changes anything. The make clean might be useful, maybe something did not get rebuilt when it should have.

jeckmann writes

I’m working on it, will let you know

Jean-Pierre

jeckmann writes

OK. It works

(my recoll is in /usr/local )

I anyway make it always with

make clean make -j8 make install

and I start it with

/usr/local/bin/recollindex -n -m -D -w 1 &

Merci,

JPEckmann

PS. Perhaps the you should change the installation script so it does some cleanrecoll?

medoc writes

Most people use the packages, so the cleanup is automatic. I really don’t know what happened here, maybe a shared library issue.

It seems rather exceptional, and adding the cleanup script to the install may cause other problems. I think that the few people adventurous enough to compile from source are not too surprised about hitting a glitch from time to time…

Maybe you would be safer following the active maintenance branch (1.20 at this time). It normally only receives bug fixes and very small and safe improvements.

I usually take a little care not to push too much crap to the trunk, but I will also just use it as a backup from time to time, and this is also where index format changes may happen, so it’s not too safe for everyday use.