Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 5 Nov 2011 14:35:41 +0100
From:      Roman Divacky <rdivacky@freebsd.org>
To:        "O. Hartmann" <ohartman@zedat.fu-berlin.de>
Cc:        Current FreeBSD <freebsd-current@freebsd.org>
Subject:   Re: FreeBSD 9.0-RC1/FreeBSD 10.0-CURRENT (amd64, CLANG): in some clients hitting backspace or arrow keys results in crashing client
Message-ID:  <20111105133541.GA65266@freebsd.org>
In-Reply-To: <4EB4F7ED.3020404@zedat.fu-berlin.de>
References:  <4EB4F7ED.3020404@zedat.fu-berlin.de>

next in thread | previous in thread | raw e-mail | index | archive | help
Can you run the crashing app under gdb and show me where it
crashes? What is the cause of the crash? SIGILL or something like
that? What instruction does it crash on?

Thank you, roman

On Sat, Nov 05, 2011 at 09:46:37AM +0100, O. Hartmann wrote:
> Operating systems in question: FreeBSD 9.0-RC1/amd64 and FreeBSD
> 10.0-CURRENT/amd64, both compiled with CLANG.
> 
> It happens that when using clients with requester for pathnames (like
> evim, thunderbird, mozilla and others) that typing some attributes into
> the requester-inputline and then hitting backspace or the arrow keys for
> editing a possibly wrong entry, the client crashes.
> 
> I realized that this very often occur with locales set to non "C".
> 
> Such a weird behaviour occured also on a Dell Latitude E6510 with
> FreeBSD 9.0-CURRENT earlier this year compiled with CLANG and compiler
> option -march=native or -march=corei7 (this laptop does have a Lynnfield
> dualCore i5 CPU). Whenever I hit backspave in the console of such a
> compiled system, the console exited and I found myself back at the login
> prompter again.
> This vanished after setting explicitely -march=core2.
> 
> The boxes now in question are both older CoreDuo architectures (Q6600
> and E8400 CPUs). The backspace/arrow-key weirdness occures not on the
> consoles anymore, but it happens that clients with files requester or
> entry fields for some data input exiting, when hitting backspace or,
> say, the back-arrow key.
> 
> Today I realized this in evim when being asked for a file to open and I
> made a typo. It seems, that the error occurs more often if the locale is
> set to non-C standard (in my case, its partially set either to
> de_DE.UTF-8 or de_DE.ISO8859-1 or en_US.UTF-8).
> 
> Regards,
> Oliver
> 





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111105133541.GA65266>