Bug 54525 - newalias - sigsegv
Summary: newalias - sigsegv
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: elm
Version: 1.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-10-11 13:28 UTC by Alexander Kanevskiy
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-10-19 18:54:00 UTC
Embargoed:


Attachments (Terms of Use)
quick fix (479 bytes, patch)
2001-10-11 13:29 UTC, Alexander Kanevskiy
no flags Details | Diff

Description Alexander Kanevskiy 2001-10-11 13:28:38 UTC
Description of Problem:

elm-2.5.6-1
Build Date: Thu Aug 23 20:16:20 2001
Build Host: stripples.devel.redhat.com

sigsegv on empty aliases.text

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

How Reproducible:

[kad@sos kad]$ mkdir .elm
[kad@sos kad]$ cd .elm
[kad@sos .elm]$ touch aliases.text
[kad@sos .elm]$ newalias
Segmentation fault
[kad@sos .elm]$ newalias
Updating your personal alias file...processed 0 aliases.
[kad@sos .elm]$ newalias
Segmentation fault
[kad@sos .elm]$ newalias
Updating your personal alias file...processed 0 aliases.
[kad@sos .elm]$ newalias
Segmentation fault
[kad@sos .elm]$ newalias
Updating your personal alias file...processed 0 aliases.
[kad@sos .elm]$


Steps to Reproduce:
1. 
2. 
3. 

Actual Results:


Expected Results:
[kad@sos .elm]$ newalias
Updating your personal alias file...processed 0 aliases.
[kad@sos .elm]$ newalias
Updating your personal alias file...processed 0 aliases.
[kad@sos .elm]$ newalias
Updating your personal alias file...processed 0 aliases.
[kad@sos .elm]$


Additional Information:
fix in attachment

Comment 1 Alexander Kanevskiy 2001-10-11 13:29:28 UTC
Created attachment 33861 [details]
quick fix

Comment 2 Trond Eivind Glomsrxd 2001-10-21 22:28:43 UTC
Thanks - fixed in elm 2.5.6-2


Note You need to log in before you can comment on or make changes to this bug.