Bug 56858 - "tree /" exits with seg.fault and dumping core.
Summary: "tree /" exits with seg.fault and dumping core.
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: tree
Version: 7.1
Hardware: ia64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-11-29 00:55 UTC by Shinya Narahara
Modified: 2008-05-01 15:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-04-23 15:55:57 UTC
Embargoed:


Attachments (Terms of Use)

Description Shinya Narahara 2001-11-29 00:55:39 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.75 [ja] (WinNT; U)

Description of problem:
On IA64 machine, the command "tree /" exits with segmentation fault and dumping core.
"tree *some directory*" can exit normally, like "/root" or so.


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


How reproducible:
Always

Steps to Reproduce:
1. tree /
2.
3.
	

Actual Results:  /
Segmentation fault (core dumped)

Expected Results:  Show all files with being tree.

Additional info:

"tree" for some directory fails, for another directory exits normally.
And on IA32 machine, this is never ocurred, for IA64 only.
The versions of tree are 1.2-11, 1.2-13, and 1.2-14, with kernel
2.4.3-12, 2.4.9-12. glibc 2.2.4-19.

Comment 1 Tim Waugh 2001-12-03 17:43:12 UTC
If you do:

gdb tree
set args /
run
bt

What does it say?


Comment 2 Shinya Narahara 2001-12-04 00:17:18 UTC
It says below:

(gdb) run
Starting program: /usr/bin/tree /
/

Program received signal SIGSEGV, Segmentation fault.
0x4000000000003581 in region_header.1 ()
(gdb) bt
#0  0x4000000000003581 in region_header.1 ()
#1  0x4000000000003570 in region_header.1 ()
(gdb) where
#0  0x4000000000003581 in region_header.1 ()
#1  0x4000000000003570 in region_header.1 ()


Comment 3 Tim Waugh 2002-05-16 13:59:45 UTC
Fixed in 1.2-18.


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