segv on lookup?

[Kenneth Brody]

On 8/8/2013 4:35 PM, Fairlight wrote:
> Top-post...
>
> The table that's been working fine until just now?  Now it's started doing
> a segv when called from the calling table that was working fine before all
> the segv nonsense started.
>
> An strace shows that it -may- be a corrupted index.

I was going to suggest that as a possibility.

> I've tried:  dxmaint pevent -ra
>
> ...But it just brings up the dxmaint menu.  I thought it was supposed to
> rebuild all indexes.

That's what the "-ra" flag does -- rebuild all auto indexes.  If you don't 
also include "-e" to exit afterwards, you will be returned to the dxmaint menu.

How many indexes are in "pevent", and how many records are in the file?  Is 
it possible that it simply rebuilt the indexes so quickly that you didn't 
see it happen?

You can always just go in w/o the "-ra" flag, and manually rebuild the 
indexes one at a time, it you aren't convinced that the previous command 
really did its job.

> How do I force that rebuild?  I think it prudent to try, before spending
> hours diagnosing something that may be a simple data corruption,
> investigating it as a code issue.
[...]

-- 
Kenneth Brody