[Top][All Lists]

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

Re: Crash when moving full-width glyphs across lines

From: Chet Ramey
Subject: Re: Crash when moving full-width glyphs across lines
Date: Sat, 21 Dec 2019 14:09:17 -0500
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.3.1

On 12/20/19 3:43 PM, Chet Ramey wrote:
> On 12/19/19 2:00 PM, Kirill Chibisov wrote:
>> I was able to capture the stack trace under gdb. However you should
>> probably use the following command in it to repro the issue.
>> `set disable-randomization off`
>> The issue happens quite randomly, however the important thing is exit code
>> from bash (139). So there's something with memory access, I guess.
>> (gdb) info stack
>> #0  0x00007fe30e6955ba in _rl_col_width (flags=<optimized out>,
>> end=1735628519, start=<optimized out>, str=0x557e988c691a "/こんにち")
>>      at
>> /usr/src/debug/sys-libs/readline-8.0_p1-r1/readline-8.0/display.c:3206
>> #1  _rl_col_width (str=0x557e988c691a "/こんにち", start=<optimized out>,
>> end=1735628519, flags=<optimized out>)
> Well, the values for `end' are obviously suspicious, but you can't really
> tell too much from this traceback, especially since other values of
> interest are optimized out. The value of `end' is computed in the caller,
> from `oe - old'. Since those are pointers into the same string, the value
> shouldn't be that far out of whack. The values of `old' and `new' are
> helpful, though. I'll see if I can find it.

I found it.

``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    address@hidden    http://tiswww.cwru.edu/~chet/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]