| delorie.com/archives/browse.cgi | search | 
| From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> | 
| Newsgroups: | comp.os.msdos.djgpp | 
| Subject: | Re: symify problem | 
| Date: | Thu, 17 Oct 2002 17:40:13 CDT | 
| Organization: | Rice University, Houston TX | 
| Lines: | 7 | 
| Message-ID: | <3daf3c4d.sandmann@clio.rice.edu> | 
| References: | <200210161723 DOT g9GHNLS04335 AT envy DOT delorie DOT com> | 
| NNTP-Posting-Host: | clio.rice.edu | 
| X-Trace: | joe.rice.edu 1034894431 25338 128.42.105.3 (17 Oct 2002 22:40:31 GMT) | 
| X-Complaints-To: | abuse AT rice DOT edu | 
| NNTP-Posting-Date: | 17 Oct 2002 22:40:31 GMT | 
| X-NewsEditor: | ED-1.5.9 | 
| To: | djgpp AT delorie DOT com | 
| DJ-Gateway: | from newsgroup comp.os.msdos.djgpp | 
| Reply-To: | djgpp AT delorie DOT com | 
> Alternately, symify could look to see if bfdsymify is in your path, > and exec it if found. I like this idea ... Should symify check the debug symbol type and warn if it's not coff and it can't find bfdsymify?
| webmaster | delorie software privacy | 
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |