*Synopsis*: ksh93 (VISUAL=vi) crashes with memory fault while scolling through
history
CR 6850672 changed on Jun 12 2009 by <User 1-1SURPB>
=== Field ============ === New Value ============= === Old Value =============
Category shell opensolaris
SubCategory korn93 triage-queue
====================== =========================== ===========================
*Change Request ID*: 6850672
*Synopsis*: ksh93 (VISUAL=vi) crashes with memory fault while scolling through
history
Product: solaris
Category: shell
Subcategory: korn93
Type: Defect
Subtype:
Status: 1-Dispatched
Substatus:
Priority: 3-Medium
Introduced In Release:
Introduced In Build:
Responsible Engineer:
Keywords: opensolaris
=== *Description* ============================================================
Category
solaris/shell (Solaris Utilities/Commands)
Sub-Category
korn93
Description
I got the lines "mcabber -f ~/.mcabber/ccc_mcabberrc_remote" and
"mcabber -f ~/.mcabber/ccc_mcabberrc_work" in my history.
Typing mc<UP> completes to the first one but I want the second one, so I
move the cursor to the 'r' of "remote" and type "d$" to delete it.
Now I type 'A' to append and want to go through the lines beginning with
"mcabber -f ~/.mcabber/ccc_mcabberrc_". After the first <UP> the cursor moves
one character back, to '_' and with a second <UP> the shell crashes.
Started from another shell I get "Memory fault(coredump)".
It's not related to the fact that mcabber is an alias for
'/opt/gentoo/usr/bin/mcabber' because it also occcurs when mcabber is executed
with its absolute path.
The coredump can be found at
http://www.zshare.net/download/61269299b237e479/
Frequency
Always
Regression
No
Steps to Reproduce
Set VISUAL=vi.
Get 2 string which differ in the last part into yout history, like "ls
/etc/ssh/ssh_host_rsa_key" and "ls /etc/ssh/ssh_host_dsa_key".
Type a few characters like "ls /etc", complete with <UP>, delete the different
part with "d$" and try to complete with <UP> again.
Expected Result
Working completion.
Actual Result
Memory fault with coredump.
Error Message(s)
Memory fault(coredump)
Test Case
Workaround
$VISUAL != vi
Additional configuration information
*** (#1 of 1): 2009-06-12 11:53:51 GMT+00:00 <User 1-F4SZV>
=== *Public Comments* ========================================================
=== *Workaround* =============================================================
=== *Additional Details* =====================================================
Targeted Release:
Commit To Fix In Build:
Fixed In Build:
Integrated In Build:
Verified In Build:
See Also:
Duplicate of:
Hooks:
Hook1:
Hook2:
Hook3:
Hook4:
Hook5:
Hook6: <email address omitted>
Program Management:
Root Cause:
Fix Affects Documentation: No
Fix Affects Localization: No
=== *History* ================================================================
Date Submitted: 2009-06-12 11:53:50 GMT+00:00
Submitted By: <User 1-F4SZV>
Status Changed Date Updated Updated By
=== *Service Request* ========================================================
Impact: Limited
Functionality: Secondary
Severity: 4
Product Name: solaris
Product Release: solaris_nevada
Product Build: snv_114
Operating System: solaris_nevada
Hardware: x86
Submitted Date: 2009-06-12 11:53:51 GMT+00:00
=== *Multiple Release (MR) Cluster* - 0 ======================================
