delorie.com/archives/browse.cgi | search |
From: | Michael Bukin <bukinm AT inp DOT nsk DOT su> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: archives? |
Date: | 26 Oct 1997 08:54:03 +0600 |
Organization: | Budker Institute of Nuclear Physics |
Lines: | 23 |
Message-ID: | <m3pvoti69g.fsf@H-Bukin.inp.nsk.su> |
References: | <01bce134$f46f11c0$c2bf13cb AT phreadd> |
<01bce160$716fe5c0$7734989e AT farout DOT demon DOT co DOT uk> | |
NNTP-Posting-Host: | aster.inp.nsk.su |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
"Richard Mitton" <richard AT farout DOT demon DOT co DOT uk> writes: > > Please! Is there ANY way to decompile the .a file into it's repective .c > > files? This is the voice of desperation! > > No. If these .c files in archive were compiled with -g switch, then you have a chance. c:\> ar x libsome.a will extract all files from archive. c:\> objdump --source some.o > some.c will produce source mixed with assembly. You can try to get rid of assembly by piping it through grep. The source may be different from the original source and may need editing. Again, you won't get any source if it was not compiled with debugging info. "ar" and "objdump" are part of the binutils (bnuXXXb.zip).
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |