Including compiled C source file in array

[sachin]

Hi,

Is it possible to do something like this:

unsigned char arr[] = {
#include "cFile.c"
}

I need that C source file cFile.c to compile and its binary output to
include in array.

How we can achieve it? Any other trick to do this?

Thanks,
Sachin

[santosh]

sachin wrote:

Hi,

Is it possible to do something like this:

unsigned char arr[] = {
#include "cFile.c"
}

I need that C source file cFile.c to compile and its binary output to
include in array.

How we can achieve it? Any other trick to do this?

You can compile cFile.c and copy it's bytes, (as hexadecimal, decimal or
octal text. All binary editors can show this for you), to your array
declaration.

Alternatively there might be compiler specific extensions for this,
though I doubt it. You might also consider the possibility of loading
the binary file at runtime with fread.

[Richard Tobin]

In article <b6************ *************** *******@u12g200 0prd.googlegrou ps.com>,
sachin <sb******@redif fmail.comwrote:

>I need that C source file cFile.c to compile and its binary output to
include in array.

What do you expect to be able to do with it?

-- Richard
--
In the selection of the two characters immediately succeeding the numeral 9,
consideration shall be given to their replacement by the graphics 10 and 11 to
facilitate the adoption of the code in the sterling monetary area. (X3.4-1963)

[Richard]

ri*****@cogsci. ed.ac.uk (Richard Tobin) writes:

In article <b6************ *************** *******@u12g200 0prd.googlegrou ps.com>,
sachin <sb******@redif fmail.comwrote:

>>I need that C source file cFile.c to compile and its binary output to
include in array.

What do you expect to be able to do with it?

-- Richard

I would expect he has something which produces code based on dynamic
variables and wants to have variable records e.g accept user tweaks,
regenerate record structures, recompile record handling SW, run record
handling SW.

[Richard Tobin]

In article <g2**********@r egistered.motza rella.org>,
Richard <rg****@gmail.c omwrote:

>>>I need that C source file cFile.c to compile and its binary output to
include in array.

>What do you expect to be able to do with it?

>I would expect he has something which produces code based on dynamic
variables and wants to have variable records e.g accept user tweaks,
regenerate record structures, recompile record handling SW, run record
handling SW.

Possibly, but unless he tells us we can't give him much help. For
most uses he'd be wisest to to use system-dependent functions that
(for example) access the symbol table, and reading the compiled file
into an array may well not be the right way to do that.

-- Richard
--
In the selection of the two characters immediately succeeding the numeral 9,
consideration shall be given to their replacement by the graphics 10 and 11 to
facilitate the adoption of the code in the sterling monetary area. (X3.4-1963)

[sachin]

On Jun 5, 5:25 pm, rich...@cogsci. ed.ac.uk (Richard Tobin) wrote:

In article <g28kua$ba...@r egistered.motza rella.org>,

Richard <rgr...@gmail.c omwrote:

>>I need that C source file cFile.c to compile and its binary output to
include in array.
What do you expect to be able to do with it?

I would expect he has something which produces code based on dynamic
variables and wants to have variable records e.g accept user tweaks,
regenerate record structures, recompile record handling SW, run record
handling SW.

Possibly, but unless he tells us we can't give him much help. For
most uses he'd be wisest to to use system-dependent functions that
(for example) access the symbol table, and reading the compiled file
into an array may well not be the right way to do that.

-- Richard
--
In the selection of the two characters immediately succeeding the numeral 9,
consideration shall be given to their replacement by the graphics 10 and 11 to
facilitate the adoption of the code in the sterling monetary area. (X3.4-1963)

Hi,

I have one C source file which after compiling I need to copy at
specific location.
Until system comes up I don't have access to that memory location. So
I want to keep
that code in executable form with the OS image. When system comes up
will copy that
executable code to designated space.

Thanks,
Sachin

[Kenny McCormack]

In article <g2***********@ pc-news.cogsci.ed. ac.uk>,
Richard Tobin <ri*****@cogsci .ed.ac.ukwrote:

>In article <b6************ *************** *******@u12g200 0prd.googlegrou ps.com>,
sachin <sb******@redif fmail.comwrote:

>>I need that C source file cFile.c to compile and its binary output to
include in array.

What do you expect to be able to do with it?

Why, to smash the stack, of course.

It's perfectly obvious that all of these queries about needing to
include (seemingly) random sequences of bytes in code are about
"cracking/hacking/freeking/whatever-you-want-to-call-it" - let's not get
into that argument...

Not necessarily for evil purposes, mind you. It's worth the exercise
just to learn what all the fuss is about.

[Jens Thoms Toerring]

sachin <sb******@redif fmail.comwrote:

On Jun 5, 5:25 pm, rich...@cogsci. ed.ac.uk (Richard Tobin) wrote:

In article <g28kua$ba...@r egistered.motza rella.org>,

Richard <rgr...@gmail.c omwrote:

>>>I need that C source file cFile.c to compile and its binary output to
>>>include in array.
>What do you expect to be able to do with it?
>I would expect he has something which produces code based on dynamic
>variables and wants to have variable records e.g accept user tweaks,
>regenerate record structures, recompile record handling SW, run record
>handling SW.

Possibly, but unless he tells us we can't give him much help. For
most uses he'd be wisest to to use system-dependent functions that
(for example) access the symbol table, and reading the compiled file
into an array may well not be the right way to do that.

I have one C source file which after compiling I need to copy at
specific location.
Until system comes up I don't have access to that memory location. So
I want to keep
that code in executable form with the OS image. When system comes up
will copy that
executable code to designated space.

You can't simply include a binary file (the C source will be
of no use anyway). Just write a little utility that opens the
file you want to insert as data at that place, reads the data
from the file in as unsigned chars and writes them out in a
form like this:

unsigned char array[ ] = {
0x01, 0x3A, 0xA6, 0x12, 0x17, 0xC3, 0x7D, 0x5F,
.....
};

Save that to a file (e.g. data.h). Then include the data.h
file at exactly the place where you want the array to be
defined. Lets hope that the binary file isn't too long to
be stored in an array.
Regards, Jens
--
\ Jens Thoms Toerring ___ [e-mail]
\______________ ____________ http://toerring.de

[Antoninus Twink]

On 5 Jun 2008 at 12:44, sachin wrote:

I have one C source file which after compiling I need to copy at
specific location.

If you're writing a virus, the man's way is to write the shellcode by
hand in assembly, not use a compiled C file.

[Flash Gordon]

Antoninus Twink wrote, On 05/06/08 17:18:

On 5 Jun 2008 at 12:44, sachin wrote:

>I have one C source file which after compiling I need to copy at
specific location.

If you're writing a virus, the man's way is to write the shellcode by
hand in assembly, not use a compiled C file.

On one DSP I used to use there was a perfectly good and "standard"
reason for wanting to achieve what the OP wants to achieve. However, the
implementation provided special tricks in the linker to allow you to
achieve it which did not involved doing what the OP asked about.

The OP needs to ask about the real problem rather than what he thinks
the solution is in a group dedicated to his implementation.
--
Flash Gordon