9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello All,
Could you please do help me here as I would like to perform parameter expansion in shell over a parameter expansion.
Let's say I have following variable.
path="/var/talend/nat/cdc"
Now to get only nat I could do following.
path1="${path%/*}"
path1="${path1##*/}"
Here... (8 Replies)
Discussion started by: RavinderSingh13
8 Replies
2. UNIX for Dummies Questions & Answers
Hey guys, thanks for lookin....my question is I want to create a macro on HPUX to SFTP a .xls to my Windows Server....I have exstensively searched and all I can find is What a macro is not how to create one.
Reasoning for having a macro is to put it in a file creation script and have it run at... (7 Replies)
Discussion started by: DStewart
7 Replies
3. UNIX for Dummies Questions & Answers
Can I create a macro in UNIX? If so where do I find out how? (1 Reply)
Discussion started by: JD_Sal
1 Replies
4. Shell Programming and Scripting
Hi ,
could anyone help me out with this problem.
sample.txt has this content :
u001- this is used for project1 ||
u002- this is used for p2|| not to be printed
u003- this is used
for project3 ||
u004- this is
used for p4 ||
u005- this is used for project5 ||
u006- this is used for p6... (9 Replies)
Discussion started by: Balaji PK
9 Replies
5. Programming
I think there is no problem to use any macro in a new macro definishion, but I have a problem with that.
I can not understand why?
I have a *.mak file that inludes file with many definitions and rules.
##############################################
include dstndflt.mak
...
One of the... (2 Replies)
Discussion started by: alex_5161
2 Replies
6. Solaris
Epic Editor was not able to obtain a license for your use. Feature Epic Editor :License server is down (1 Reply)
Discussion started by: durgaprasadr13
1 Replies
7. Shell Programming and Scripting
Hi All,
I am running a script , working very fine on cmd prompt. The problem is that when I open do crontab -e even after setting editor to vi by
set EDITOR=vi it does not open a vi editor , rather it do as below.....
/////////////////////////////////////////////////////
$ set... (6 Replies)
Discussion started by: aarora_98
6 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I knw its a silly question, but am a newbie to 'vi' editor. I'm forced to use this, hence kindly help me with this question.
How can i paste a chunk 'copied from' a different editor(gedit) in 'vi editor'?
As i see, p & P options does work only within 'vi'. (10 Replies)
Discussion started by: harishmitty
10 Replies
9. Programming
Can i define a macro for a function of 10 LOC. (9 Replies)
Discussion started by: bankpro
9 Replies
GET_END(3) Library Functions Manual GET_END(3)
NAME
get_end, get_etext, get_edata - get values of UNIX link editor defined symbols
SYNOPSIS
#include <mach-o/getsect.h>
unsigned long get_end();
unsigned long get_etext();
unsigned long get_edata();
DESCRIPTION
These routines provide a stopgap measure to programs that use the UNIX link-editor defined symbols. Use of these routines is very strongly
discouraged. The problem is that any program that is using UNIX link editor defined symbols (_end, _etext or _edata) is making assumptions
that the program has the memory layout of a UNIX program.
This is an incorrect assumption for a program built by the Mach-O link editor. The reason that these routines are provided is that if very
minimal assumptions about the layout are used and the default format and memory layout of the Mach-O link editor is used to build the pro-
gram, some things may work by using the values returned by these routines in place of the addresses of their UNIX link-editor defined sym-
bols. So use at your own risk, and only if you know what your doing. Or better yet, convert the program to use the appropriate Mach or
Mach-O functions. If you are trying to allocate memory use vm_allocate(2), if you are trying to find out about your address space use
vm_region(2) and if you are trying to find out where your program is loaded use the dyld(3) functions.
The values of the UNIX link-editor defined symbols _etext, _edata and _end are returned by the routines get_etext, get_edata, and get_end
respectively. In a Mach-O file they have the following values: get_etext returns the first address after the (__TEXT,__text) section, note
this my or may not be the only section in the __TEXT segment. get_edata returns the first address after the (__DATA,__data) section, note
this my or may not be the last non-zero fill section in the __DATA segment. get_end returns the first address after the last segment in
the executable, note a shared library may be loaded at this address.
SEE ALSO
ld(1), dyld(3)
Apple Computer, Inc. April 10, 1998 GET_END(3)