From: <ams AT ludd DOT luth DOT se>
Message-Id: <200212251235.gBPCZSY25079@speedy.ludd.luth.se>
Subject: Re: Symify calling bfdsymify
In-Reply-To: <3E05CCA1.884B30AE@yahoo.com> "from CBFalconer at Dec 22, 2002 09:30:57
 am"
To: djgpp-workers AT delorie DOT com
Date: Wed, 25 Dec 2002 13:35:28 +0100 (CET)
X-Mailer: ELM [version 2.4ME+ PL78 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
X-MailScanner: Found to be clean
X-MailScanner-SpamScore: s
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

According to CBFalconer:
> Martin Str|mberg wrote:
> > 
> > Here's a patch to make symify call bfdsymify:
> 
> Why?  With 4dos I simply create an alias.  Without 4dos a batch
> file should do the same thing.

Because it's been discussed on this list and IIRC sounded like a good
idea, because all the documentation says to run symify when you get a
crash and we can't be sure that the user have installed gdb*b.zip.

So try bsdsymify and fall back to the old code if it's not there.

As for the C code and not some .BAT file, I know C and not much about
.BATs.


Right,

						MartinS