Sponsored Content
Full Discussion: C
Top Forums Programming C Post 7657 by loadc on Friday 28th of September 2001 10:47:58 PM
Old 09-28-2001
EEEKKK!!!

Okay, I've wanted to do this as well-

Here is the trick the VM mainframeers taught me, it actually did work, but keep in mind, I did this on a VM CP command env, using pipes and some VM tools translating to EBCDIC, so go easy if this doesn't translate well...

We took the binary file and converted to hex sing a converter in the editor on VM, we then took the hex and translated to EBCDIC (ascii should be a reasonable change from there, as well), and read what we could of the file.

Keep in mind, teh compiler that put the file together is going to have done some things to the file, you are WAY better off with a good de-compiler, but you didn't hear that from me...

Whatever you get back from either operation, it may not be an exact copy of the source code, unless you have a lot of time, knowledge of EXACTLY what tools were used by the developers, and the skill or luck to find a de-compiler that knows what the compiler did.


Or, maybe I'm totally out of my tree and I'm talking out of my knothole...



loadc
 
uil(1X) 																   uil(1X)

NAME
uil - The user interface language compiler SYNOPSIS
uil [options] file DESCRIPTION
The uil command invokes the UIL compiler. The User Interface Language (UIL) is a specification language for describing the initial state of a user interface for a Motif application. The specification describes the objects (menus, dialog boxes, labels, push buttons, and so on) used in the interface and specifies the routines to be called when the interface changes state as a result of user interaction. Speci- fies the file to be compiled through the UIL compiler. Specifies one or more of the following options: This option causes the compiler to look for include files in the directory specified if the include files have not been found in the paths that already were searched. Specify this option followed by a pathname, with no intervening spaces. Machine code is listed. This directs the compiler to place in the listing file a description of the records that it added to the User Interface Database (UID). This helps you isolate errors. The default is no machine code. Directs the compiler to produce a UID. By default, UIL creates a UID with the name a.uid. The file specifies the filename for the UID. No UID is produced if the compiler issues any diagnostics categorized as error or severe. Directs the compiler to set the locale before compiling any files. The locale is set in an implementation-dependent manner. On ANSI C-based systems, the locale is usually set by calling setlocale(LC_ALL, " "). If this option is not specified, the compiler does not set the locale. Directs the compiler to gen- erate a listing. The file specifies the filename for the listing. If the -v option is not present, no listing is generated by the compiler. The default is no listing. Specifies that the compiler suppress all warning and informational messages. If this option is not present, all messages are generated, regardless of the severity. Specifies a binary widget meta-language description file to be used in place of the default WML description. For more information about UIL syntax, see the OSF/Motif Programmer's Guide. SEE ALSO
X(1X), Uil(3X) uil(1X)
All times are GMT -4. The time now is 11:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy