Closed Bug 349 Opened 26 years ago Closed 26 years ago

Segmentation fault if can't get current directory

Categories

(MozillaClassic Graveyard :: XFE, defect, P3)

Product:
MozillaClassic Graveyard
Version:
1998-04-29
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED WONTFIX

People

(Reporter: mfg, Assigned: mcafee)

Details

Created by Michael Gordon (mfg@ee.ed.ac.uk) on Wednesday, May 13, 1998 6:15:17 AM PDT
Additional Details :
There's a segmentation fault in strlen() at line 4915
of cmd/xfe/mozilla.c if the previous getcwd() fails.
Is setting 'string' to '.' if getcwd() fails acceptable?
Status: NEW → ASSIGNED
Component: Platform: Rhapsody → XFE
I put an assert in here for now, yeah there's a segfault possibility.
Do you have a case where this happens so I can test this?
Sorry it took so long for me to get to this bug.
[from mfg]
Just do

  mkdir /tmp/foo
  mkdir /tmp/foo/foo2
  chmod 111 /tmp/foo
  cd /tmp/foo/foo2
  moz-export

I discovered this when other people tried to run the mozilla binary I'd
compiled under my home directory, which is mode 711.  I don't know how
likely it is that this bug would be triggered in normal use.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → WONTFIX
xfe is gone in the new world.
Status: RESOLVED → VERIFIED
Marking Verified/Won't Fix
You need to log in before you can comment on or make changes to this bug.