Port-arm archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: ongoing vi issues ....

In article <552D3243.1040803%hiwaay.net@localhost>,
William A. Mahaffey III <wam%hiwaay.net@localhost> wrote:
>On 04/14/15 09:43, Christos Zoulas wrote:
>> In article <552D17BB.6030406%hiwaay.net@localhost>,
>> William A. Mahaffey III <wam%hiwaay.net@localhost> wrote:
>>> Apr 14 08:25:46 kabini1 kernel: pid 1517 (rxvt), uid 1110: exited on
>>> signal 11
>>> Apr 14 08:26:22 kabini1 kernel: pid 2099 (rxvt), uid 1110: exited on
>>> signal 11
>>> The last 2 lines are from the crashed session on the NetBSD box ....
>>> This could well be some obscure case of incompatible interactions,
>>> however it *is* a plague for me :-/ .... Need anything else, please ask.
>>> TIA & have a good one ....
>> Yes, but the crash is on the FreeBSD side. Try using xterm instead of rxvt
>> or ask for help in the FreeBSD lists.
>> christos
>Yeah, but it only happens when shelled into NetBSD-7 on the RPiB+, 
>nowhere else, including various linux boxen, i.e. it seems to be the 
>specific combo of ssh in from FBSD 9.3R under rxvt/tcsh *to* NetBSD-7 
>evbarm-earmv6hf .... i.e. only unique factor is NetBSD-7 (beta :-) ) 
>involvement ....

I understand, but the code is not running on NetBSD. You'll have to
debug what is wrong on the FreeBSD side. You could compile rxvt on
FreeBSD with debugging and use gdb on it. Also as I suggested you
should try to use xterm to see if the problem is particular to rxvt
or it is something in the x libraries that affects more stuff.

It is like you are hitting a nail with the hammer, the hammer breaks
and you blame the nail.


Home | Main Index | Thread Index | Old Index