08-31-2006
Okay. Let's assume the linux box had a different, earlier version of the source you are compiling - by accident. How can you tell you're building the app from the correct source? Since the result is the same, your methods say nothing changed, then you are left with one answer: compiling the wrong version of code.
8 More Discussions You Might Find Interesting
1. Programming
At time of installation I have to open the resource. and i have to insert a string serial number in the exe.
please provide me code to edit the exe (in solaris) to insert a serial number which can be used by exe at run time. (6 Replies)
Discussion started by: ssahu
6 Replies
2. HP-UX
im not good with this stuff but the app guys game to me with a problem with there c++ program on a new box, any ideas?
bin- ./qeng
Bus error (core dumped)
bin- ./gdb qeng core
Wildebeest is free software and you are welcome to distribute copies of
it under certain conditions; type "show... (4 Replies)
Discussion started by: csaunders
4 Replies
3. Red Hat
Hello,
I'm experimenting a problem on my rh server.
Red Hat Enterprise Linux AS release 3 (Taroon Update 8)
2.4.21-47.ELsmp #1 SMP i686 i686 i386 GNU/Linux
It started with a segmentation fault on
#id root
To resolve it, I've installed
coreutils-4.5.3-28.4.i386.rpm
But, I... (6 Replies)
Discussion started by: gogol_bordello
6 Replies
4. Programming
for example, I have a static lib name liba.a
it offers some interface such a1();a2();
but i do not have the source code of liba.a;
If i would like to create a shared object, and offer the similar interface of
a1 and a2;
Is there a way to fulfill such requirement?
thanks. (7 Replies)
Discussion started by: flost
7 Replies
5. Solaris
When loooking at files in a directory using ls, how can I tell if I have a hard link or soft link? (11 Replies)
Discussion started by: Harleyrci
11 Replies
6. Shell Programming and Scripting
I have a C++ binary executable installed in a file system which is shared across multiple solaris boxes.
When I start this executable from one of the boxes,I am able to start only 4 parallel instances and from the 5th instance onwards I am getting the following error.
fatal: libdb2.so.1:... (2 Replies)
Discussion started by: prasperl
2 Replies
7. AIX
Hi
I'm logged in as root in an aix box
Which command will list all the soft links and hard links present in the server ? (2 Replies)
Discussion started by: newtoaixos
2 Replies
8. Programming
Hello.
I am new to this forum and I would like to ask for advice about low level POSIX programming.
I have to implement a POSIX compliant C shared library.
A file will have some variables and the shared library will have some functions which need those variables.
There is one special... (5 Replies)
Discussion started by: iamjag
5 Replies
LEARN ABOUT DEBIAN
ragg2-cc
RAGG2-CC(1) BSD General Commands Manual RAGG2-CC(1)
NAME
ragg2-cc -- CC frontend for compiling shellcodes
SYNOPSIS
ragg2-cc [-a arch] [-b bits] [-k kernel] [-o file] [-dscxvh]
DESCRIPTION
ragg2-cc is a frontend of CC. It is used to creates tiny binaries (1KB) or shellcodes in binary or hexpairs from a C source.
The compiler used is the one configured by the CC environment. This has been tested with gcc, llvm-gcc and clang.
Uses sflib (shellforge4) includes to get the syscall definitions.
Only linux/darwin x86-32/64 is supported at the moment. Planned support for more architectures.
OPTIONS
-a arch set architecture x86, arm
-b bits 32 or 64
-k kernel windows, linux or osx
-o file output file to write result of compilation
-h show help message
-v show version
-d show assembler code
-s generate assembly file
-c generate compiled shellcode
-x show hexpair bytes
EXAMPLE
$ cat hi.c
int main() {
write (1, "Hello World
", 12);
exit (0);
}
$ ragg2-cc hi.c
hi.c.bin
# Linked into a tiny binary. This is 294 bytes
$ wc -c < hi.c.bin
294
$ ./hi.c.bin
Hello World
# The compiled shellcode has zeroes
$ ragg2-cc -x hi.c
e90000000083ec0ce800000000588d882a000000b804000000606a0651
6a0150cd8083c41061b8010000006a0050cd8083c40883c40cc368656c
6c6f0a00
# Use a xor encoder with key 32 to bypass
$ ragg2 -e xor -c key=32 -B `ragg2-cc -x hi.c`
6a3e596a205be8ffffffffc15e4883c60d301e48ffc6e2f9c920202020
a3cc2cc82020202078ada80a2020209824202020404a26714a2170eda0
a3e4304198212020204a2070eda0a3e428a3e42ce348454c4c4f2a20
SEE ALSO
radare2(1), rahash2(1), rafind2(1), rabin2(1), rafind2(1), ranal2(1), radiff2(1), rasm2(1), ragg2cc(1),
AUTHORS
pancake <pancake@nopcode.org>
BSD
Dec 5, 2011 BSD