home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!wupost!zaphod.mps.ohio-state.edu!uwm.edu!ogicse!psgrain!onion!pail!servio!penneyj
- From: penneyj@slc.com (D. Jason Penney)
- Newsgroups: comp.unix.wizards
- Subject: Re: a dbx internal error
- Message-ID: <1992Jul27.022411.479@slc.com>
- Date: 27 Jul 92 02:24:11 GMT
- Article-I.D.: slc.1992Jul27.022411.479
- References: <1992Jul25.232154.5123@jhunix.hcf.jhu.edu>
- Distribution: usa
- Organization: Servio Corp, Beaverton Oregon, US
- Lines: 32
-
-
- In comp.unix.wizards you write:
-
- >Reading symbolic information...
- >dbx: internal error: unexpected value 38 at line 2620 in file ../common/object.c
-
- >I ran into this on SunOS 4.1.1. I do not have ../common from where i am
- >running dbx. Any tips or pointers to more appropriate groups would
- >be appreciated.
-
- I'm not trying to be facetious; the best answer to your problem is,
-
- chmod ugo-x /usr/ucb/dbx
- cp gdb /usr/bin; chmod 555 gdb
-
- In other words, get a copy of gdb and let dbx go to the wastebasket.
- In case you haven't already discovered this, dbx writes on your executable
- disk file, so if it crashes (as you have had it do), you must delete and
- rebuild the executable file.
-
- This in itself is heinous enough to warrant removing execute permission on
- the file. gdb does NOT write on the file being debugged.
-
- Finally, the port of gdb to SunOS 4.1.1 is exceptionally stable and
- reliable.
-
- 'nuff said!
-
- --
- D. Jason Penney Ph: (503) 629-8383
- Beaverton, OR 97006 uucp: ...uunet!servio!penneyj (penneyj@slc.com)
- "Talking about music is like dancing about architecture." -- Steve Martin
-