Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1321141 - tcsh crash with command completion
Summary: tcsh crash with command completion
Keywords:
Status: CLOSED DUPLICATE of bug 1303323
Alias: None
Product: Fedora
Classification: Fedora
Component: tcsh
Version: 24
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: David Kaspar // Dee'Kej
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-24 18:47 UTC by jared mauch
Modified: 2016-04-05 12:56 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-05 12:56:09 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description jared mauch 2016-03-24 18:47:05 UTC 
Description of problem:

tcsh crash when pressing tab to complete

Version-Release number of selected component (if applicable):

tcsh-6.19.00-4.fc24.x86_64

How reproducible:
Always

Steps to Reproduce:
1. start tcsh
2. press tab
3. crash

Actual results:
crash

Expected results:
should display command completion options for commands in $path, or if after the first token, files in $cwd

Additional info:

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7674558 in rewinddir () from /lib64/libc.so.6
(gdb) bt
#0  0x00007ffff7674558 in rewinddir () from /lib64/libc.so.6
#1  0x0000555555580d85 in tw_file_start ()
#2  0x00005555555828fc in tw_collect ()
#3  0x0000555555583e45 in t_search ()
#4  0x0000555555584e97 in tenematch ()
#5  0x0000555555594404 in Inputl ()
#6  0x000055555557288a in readc.part ()
#7  0x0000555555575397 in lex ()
#8  0x000055555555d60f in process ()
#9  0x000055555555c445 in main ()
Comment 1 jared mauch 2016-04-05 12:56:09 UTC 

*** This bug has been marked as a duplicate of bug 1303323 ***
Note You need to log in before you can comment on or make changes to this bug.