| delorie.com/archives/browse.cgi | search |
| From: | Cesar Rabak <csrabak AT uol DOT com DOT br> |
| Newsgroups: | comp.os.msdos.djgpp |
| Subject: | Re: symify problem |
| Date: | Sat, 19 Oct 2002 22:21:51 -0300 |
| Lines: | 17 |
| Message-ID: | <3DB2052F.CDB53883@uol.com.br> |
| References: | <200210161723 DOT g9GHNLS04335 AT envy DOT delorie DOT com> <3daf3c4d DOT sandmann AT clio DOT rice DOT edu> |
| NNTP-Posting-Host: | 200-221-14-196.speedy.speeduol.com.br (200.221.14.196) |
| Mime-Version: | 1.0 |
| X-Trace: | fu-berlin.de 1035076847 26612116 200.221.14.196 (16 [39218]) |
| X-Mailer: | Mozilla 4.79 [en] (Win98; U) |
| X-Accept-Language: | pt-BR,es,en |
| To: | djgpp AT delorie DOT com |
| DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
| Reply-To: | djgpp AT delorie DOT com |
Charles Sandmann wrote: > > > 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? If this does not gets into a new one thousons man hours project I vote yes ;-) -- Cesar Rabak GNU/Linux User 52247. Get counted: http://counter.li.org/
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |