unix command for multifile program execution

Thread Tools Search this Thread
Operating Systems Linux unix command for multifile program execution
# 1  
Old 02-01-2008
Bug unix command for multifile program execution

how can I compile and execute multifile program in unix os.Smilie
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Programming

Help with C++ program execution.

//Find the root of the equation (x^2)-2 by bisection method. #include<iostream> using namespace std; double a,x; double f(double x) { return ((x*x)-2); } //Suppose the function is (x*x)-2. void calcx(double a1,double b1) { x =... (2 Replies)
Discussion started by: poonam.gaigole
2 Replies

2. Shell Programming and Scripting

Remote access and command execution on unix platform

How can we create new directory/Or execute command on remote unix machine from another unix machine. We can use SSH command to execute command on remote machine but problem is that ssh will prompt for password before executing command. My requirment is to execute command without manual... (1 Reply)
Discussion started by: pasricha.kunal
1 Replies

3. UNIX for Dummies Questions & Answers

UNIX command to skip any warning messages and continue job execution

Hello All, Good day! This is my first UNIX post. :D Anyways, I would like to seek help from you guys if you know of any UNIX command that will skip a warning message once it is encountered but continue to run the execution. Ok here's the situation in general: An encypted file is sent to... (2 Replies)
Discussion started by: jennah_rekka
2 Replies

4. UNIX for Advanced & Expert Users

UNIX Queue command execution

Hello, i was wondering if you could assist me in the following situation: i am trying to queue a group execution commands (same command but different parameters) submited from an openVMS system to a Unix system (HP UX). The commands should run in sequence; the next starts after prev finish... (5 Replies)
Discussion started by: wede23
5 Replies

5. Programming

A program to trace execution of another program

Hi, I wanted to know if i can write a program using switches and signals, etc to trace execution of other unix program which calls c program internally. If yes how? If not with signals and switches then are there any other methods apart from debugging with gdb/dbx. (3 Replies)
Discussion started by: jiten_hegde
3 Replies

6. UNIX for Dummies Questions & Answers

How to develop C program using UNIX command

hai friend, I am new to linux... I have to develop C program using unix command and i know the SYSTEM command.. But i need other then SYSTEM comand, plz send me the sample code.... Thank you.. sundar (1 Reply)
Discussion started by: sundar.lsr
1 Replies

7. UNIX for Dummies Questions & Answers

multifile c program compilation and execution

i am using unix os and my program is divided in two text files .:):) how to compile and make one executable file, using unix command. (1 Reply)
Discussion started by: alokmishra8
1 Replies

8. Programming

execution small C++ program in UNIX

Hi my friends I am beginner unix programmer I have written small c++ program in text editor and I have change it mode to 555 to make it executable file to use it in unix O.P. #include<iostream.h> main() { cout<<"Hello World"; } but some syntax erroe came for << can any one help... (5 Replies)
Discussion started by: bintaleb
5 Replies

9. Programming

man pages of any command from a c program in unix

i wanted to display the man pages of any command in unix from a c program.can some one help me plzzzzzz. (2 Replies)
Discussion started by: spanduu
2 Replies

10. UNIX for Dummies Questions & Answers

Java program calling a UNIX command

I was wondering if it was possible to call a unix command directly from a Java program during run-time. This command could very very basic e.g. "ps -ef" returned as a string, all I need is a starting place so if anyone has any suggestion or examples I would be very grateful (2 Replies)
Discussion started by: QUartz Ite
2 Replies
Login or Register to Ask a Question
dwz(1)							      General Commands Manual							    dwz(1)

       dwz - DWARF optimization and duplicate removal tool

       dwz [OPTION...] [FILES]

       dwz  is	a program that attempts to optimize DWARF debugging information contained in ELF shared libraries and ELF executables for size, by
       replacing DWARF information representation with equivalent smaller representation where possible and by reducing the amount of  duplication
       using techniques from DWARF standard appendix E - creating DW_TAG_partial_unit compilation units (CUs) for duplicated information and using
       DW_TAG_imported_unit to import it into each CU that needs it.

       The tool handles DWARF 32-bit format debugging sections of versions 2, 3 and 4 and GNU extensions on top of those, though using DWARF 4	or
       worst case DWARF 3 is strongly recommended.

       The  tool  has  two main modes of operation, without the -m option it attempts to optimize DWARF debugging information in each given object
       (executable or shared library) individually, with the -m option it afterwards attempts to optimize even	more  by  moving  DWARF  debugging
       information  entries (DIEs), strings and macro descriptions duplicated in more than one object into a newly created ELF ET_REL object whose
       filename is given as -m option argument.  The debug sections in the executables and shared libraries specified on the command line are then
       modified again, referring to the entities in the newly created object.

       -m FILE --multifile FILE
	      Multifile  mode.	 After	processing all named executables and shared libraries, attempt to create ELF object FILE and put debugging
	      information duplicated in more than one object there, afterwards optimize each named executable or shared library  even  further	if

       -h --hardlink
	      Look  for  executables  or shared libraries hardlinked together, instead of rewriting them individually rewrite just one of them and
	      hardlink the rest to the first one again.

       -M NAME --multifile-name NAME
	      Specify the name of the common file that should be put into the .gnu_debugaltlink section alongside with its build ID.   By  default
	      dwz puts there the argument of the -m option.

       -r --relative
	      Specify  that  the  name	of  the  common file to be put into the .gnu_debugaltlink section is supposed to be relative path from the
	      directory containing the executable or shared library to the file named in the argument of the -m option.  Either -M  or	-r  option
	      can be specified, but not both.

       -q --quiet
	      Silence up some of the most common messages.

       -o FILE --output FILE
	      This  option  instructs dwz not to overwrite the specified file, but instead store the new content into FILE.  Nothing is written if
	      dwz exits with non-zero exit code.  Can be used only with a single executable or shared library (if there are no arguments  at  all,
	      a.out is assumed).

       -l COUNT --low-mem-die-limit COUNT
	      Handle executables or shared libraries containing more than COUNT debugging information entries in their .debug_info section using a
	      slower and more memory usage friendly mode and don't attempt to optimize that object in multifile mode.  The default is  10  million
	      DIEs.  There is a risk that for very large amounts of debugging information in a single shared library or executable there might not
	      be enough memory (especially when dwz tool is 32-bit binary, it might run out of available virtual address space even sooner).

       -L COUNT --max-die-limit COUNT
	      Don't attempt to optimize executables or shared libraries containing more than COUNT DIEs at all.  The default is 50 million DIEs.

       -? --help
	      Print short help and exit.

       Command-line arguments should be the executables, shared libraries or their stripped to file separate debug information objects.

	      $ dwz -m .dwz/foobar-1.2.debug -rh 
		bin/foo.debug bin/foo2.debug foo/lib/libbar.so.debug
       will attempt to optimize debugging information in bin/foo.debug, bin/foo2.debug and lib/libbar.so.debug (by modifying the files	in  place)
       and  when  beneficial  also  will  create  .dwz/foobar-1.2.debug  file.	 .gnu_debugaltlink  section  in  the first two files will refer to
       ../.dwz/foobar-1.2.debug and in the last file to ../../.dwz/foobar-1.2.debug.  If e.g.  bin/foo.debug and  bin/foo2.debug  were	hardlinked
       together initially, they will be hardlinked again and for multifile optimizations considered just as a single file rather than two.
	      $ dwz -o foo.dwz foo
       will not modify foo but instead store the ELF object with optimized debugging information if successful into foo.dwz file it creates.
	      $ dwz *.debug foo/*.debug
       will attempt to optimize debugging information in *.debug and foo/*.debug files, optimizing each file individually in place.
	      $ dwz
       is equivalent to dwz a.out command.

       http://dwarfstd.org/doc/DWARF4.pdf , gdb(1).

       Jakub Jelinek <jakub@redhat.com>.

								   15 June 2012 							    dwz(1)