Re: [dev] [st] Reporting a Segmentation fault

From: Marc Collin <marc.collin7_AT_gmail.com>
Date: Fri, 20 Nov 2015 11:41:42 -0200

Following up, the backtrace. I wish this helps. Let me know what else
I can do. Thanks.

erresc: unknown sequence ESC 0xFD '.'
./seg_wrapper.sh: line 3: 2870 Segmentation fault (core dumped) "$_AT_"
Reading symbols from st...done.
[New LWP 2870]

warning: Can't read pathname for load map: No error information.
Core was generated by `st'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 utf8decode (
    c=0x4762fb62000 <error: Cannot access memory at address 0x4762fb62000>,
    u=0x772fc35eccf4, clen=18446744073709542299) at st.c:617
617 udecoded = utf8decodebyte(c[0], &len);
#0 utf8decode (
    c=0x4762fb62000 <error: Cannot access memory at address 0x4762fb62000>,
    u=0x772fc35eccf4, clen=18446744073709542299) at st.c:617
#1 0x000004762f9590d7 in ttyread () at st.c:1484
#2 0x000004762f959667 in run () at st.c:4264
#3 0x000004762f95417b in main (argc=0, argv=<optimized out>) at st.c:4402

On Fri, Nov 20, 2015 at 11:33 AM, Marc Collin <marc.collin7_AT_gmail.com> wrote:
> v4hn - sorry. my terminfo is version 6.0. my kernel has the grsec
> patch. I'll try to see if I can get a backtrace as you request.
>
> Martii - my vimrc is simple.
> set nocompatible, set bs=2, set history=50, set ruler and set
> nomodeline. That's all I have.
>
>
>
>
> On Fri, Nov 20, 2015 at 11:20 AM, Martti Kühne <mysatyre_AT_gmail.com> wrote:
>> On Fri, Nov 20, 2015 at 2:09 PM, Marc Collin <marc.collin7_AT_gmail.com> wrote:
>>> I am using the grsec kernel, for better security. Maybe st doesn't
>>> play well with that?
>>> Just tested on a clean st and it segfaults too.
>>>
>>
>> I'm not familiar with the details of grsecurity, but it's definitely
>> not about parsing escape sequences.
>> Do you have a .vimrc or /etc/vimrc file, and if you have, can we get it?
>>
>> cheers!
>> mar77i
>>
Received on Fri Nov 20 2015 - 14:41:42 CET