Re: Alignment error comm=vi

[Darren Reed <darrenr%netbsd.org@localhost>]

On 12/06/2014 9:21 PM, Martin Husemann wrote:
> On Thu, Jun 12, 2014 at 09:14:44PM +1000, Darren Reed wrote:
>> Alignment error: pid=631.1 comm=vi dsfsr=00000000:00800001
>> dsfar=ffffffff:fec5d1f9 isfsr=00000000:00808000 pc=10892c
> 
> Can you reproduce it? If so, how?

Easily.

Alignment error: pid=631.1 comm=vi dsfsr=00000000:00800001
dsfar=ffffffff:fec5d1f9 isfsr=00000000:00808000 pc=10892c
Alignment error: pid=682.1 comm=vi dsfsr=00000000:00800001
dsfar=ffffffff:fec5d3bd isfsr=00000000:00808000 pc=10892c
Alignment error: pid=689.1 comm=vi dsfsr=00000000:00800001
dsfar=ffffffff:fec5b339 isfsr=00000000:00808000 pc=10892c
Alignment error: pid=226.1 comm=vi dsfsr=00000000:00800001
dsfar=ffffffff:fec55525 isfsr=00000000:00808000 pc=10892c
Alignment error: pid=663.1 comm=vi dsfsr=00000000:00800001
dsfar=ffffffff:fec5c39d isfsr=00000000:00808000 pc=10892c

If I do "u" to undo in vi, more often than not it core dumps.

It has been doing this ever since I installed, I just never
looked at the console before to see if it was printing anything
when vi crashed.

Core was generated by `vi'.
Program terminated with signal 10, Bus error.
#0  0x000000000010892c in default_int2char.clone.1 ()
(gdb) where
#0  0x000000000010892c in default_int2char.clone.1 ()
#1  0x0000000000154418 in db_set ()
#2  0x0000000000155504 in log_backward ()
#3  0x0000000000143e54 in vi ()
#4  0x000000000012aaac in editor ()
#5  0x0000000000106514 in main ()

Cheers,
Darren