home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.sun.misc:4166 comp.sys.sun.apps:1881
- Path: sparky!uunet!crdgw1!rdsunx.crd.ge.com!rdsunx!barnett
- From: barnett@grymoire.crd.ge.com (Bruce Barnett)
- Newsgroups: comp.sys.sun.misc,comp.sys.sun.apps
- Subject: Re: Why is .dbxinit read before symbol table?
- Message-ID: <BARNETT.92Sep10093357@grymoire.crd.ge.com>
- Date: 10 Sep 92 14:33:57 GMT
- References: <las68iINN42n@news.bbn.com>
- Sender: usenet@crd.ge.com (Required for NNTP)
- Reply-To: barnett@crdgw1.ge.com
- Organization: GE Corp. R & D, Schenectady, NY
- Lines: 17
- In-Reply-To: wsadkin@bbn.com's message of 9 Sep 92 15:32:34 GMT
- Nntp-Posting-Host: grymoire.crd.ge.com
-
- In article <las68iINN42n@news.bbn.com> wsadkin@bbn.com (Will Sadkin) writes:
- > Can anyone tell me why the .dbxinit file (or -s <startup file>) is read
- > *prior* to reading the symbol table for the program being debugged? To
-
- I use my ~/.dbxinit it to define a set of projects. Each one is
- associated with a button or menu choice. I can then click on a button
- and "goto" the proper directory, read the local .dbxinit file, etc.
- Since you can switch from debugging one executable to another on the
- fly, it makes sense that the startup of dbx should be separated from
- reading the symbol table.
-
-
- You can do the same thing by adding a button that does the
- "source .mydbxinit" file on command, or make an alias for it.
-
- --
- Bruce Barnett <barnett@crd.ge.com> uunet!crdgw1!barnett
-