Bug 173023 - gctags --cxref option causes segmentation fault
Summary: gctags --cxref option causes segmentation fault
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: emacs
Version: 4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jens Petersen
QA Contact:
URL:
Whiteboard:
: 173022 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-11-12 17:33 UTC by Hideki IWAMOTO
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version: 21.4-14
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-03-28 03:56:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Hideki IWAMOTO 2005-11-12 17:33:43 UTC
Description of problem:
gctags causes segmentation fault when --cxref(-x) option is used.

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


How reproducible:
Use --cxref(-x) option.

Steps to Reproduce:
1.touch a.c
2.gctags -x a.c

  
Actual results:
Segmentation fault

Expected results:

Additional info:

Comment 1 Hideki IWAMOTO 2005-11-12 17:35:44 UTC
*** Bug 173022 has been marked as a duplicate of this bug. ***

Comment 2 Hideki IWAMOTO 2005-11-12 17:47:36 UTC
ctags inclued in emacs-21.4 does not have this bug.
This bug was introduced by etags-14.21-17.11-diff.patch.

A patch was posted to emacs-pretest-bug about 1 week ago.
But emacs people seem to have no interest in this.
http://lists.gnu.org/archive/html/emacs-pretest-bug/2005-11/msg00063.html

Comment 3 Hideki IWAMOTO 2005-11-18 15:01:20 UTC
This bug was fixed in upstream etags.
http://savannah.gnu.org/cgi-bin/viewcvs/emacs/emacs/lib-src/etags.c.diff?
r1=3.49&r2=3.50&sortby=date


Comment 4 Jens Petersen 2005-11-22 02:44:16 UTC
Ok, thanks for the report.

Updating to latest etags.c in next build.

Comment 5 Jens Petersen 2005-11-24 04:07:03 UTC
Updating to latest etags.c code in next devel build.
Should be in emacs-21.4-9.

Comment 6 Jens Petersen 2006-03-28 03:56:49 UTC
Fix should be in FC5.


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