Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <4033AEE3.35875E0C@dessent.net> Date: Wed, 18 Feb 2004 10:28:51 -0800 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Assembler References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Krzysztof Duleba wrote: > A translator that changes int 0x80 to function calls? It doesn't seem too > difficult, but I probably miss something. So write a perl script. The list of syscalls is defined in the Linux kernel in unistd.h: You may also want to read these pages: > The way I think is: if in Linux it is possible to translate function calls > to int 0x80, one could build a funcion call -> int 0x80 dictionary. If the > dictionary is complete (or at least big enough), having a int 0x80-like > system call one can look up the corresponding funcion call. I don't know what you're trying to do here but it sounds like it's not going to work. If you're trying to compile code written in assember then you should have the source with symbolic calls and not raw syscalls, otherwise the person writing the code was an idiot. If you're trying to decompile and port some random linux binary to run under Cygwin, then I must conclude that you're nuts. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/