#include <stdio.h>
main() {
static int n;
n = 6;
printf("hello %d\n", n);
n=7;
}
### snip
64 bit compile/link....
Code:
$ export OBJECT_MODE=64
$ cc -g -o hello hello.c
$ gdb ./hello
(gdb) b 8
Breakpoint 1 at 0x1000004a4: file hello.c, line 8.
(gdb) r
Starting program: /src/kiwi_7.94_01oct2014/hello
Breakpoint 1, main () at hello.c:8
8 printf("hello %d\n", n);
(gdb) p n
Cannot access memory at address 0x10000708
(gdb)
If you take off the "static" on line 4, it works fine.
Also it works fine in 32 bit mode.
Moderator's Comments:
Please use CODE tags when displaying sample input, output, and code segments.
Last edited by Don Cragun; 09-08-2014 at 04:42 PM..
Reason: Add CODE tags.
Hi
I am using solaris 8 and I need to create 64-bit executable 'lsof'.
what is the cc equivalent option? and
how to check whether my compiler supports 64-bit executables or not?
Thanks in advance (1 Reply)
Hi All
I have a structure pointer and setting that pointer as NULL. When i tried to access the elements in the structure i am getting the error message.
"Cannot access memory at address 0x8". This i tried in LINUX.
When the same program is tried thro UNIX (HP-UX), i am not getting the message... (8 Replies)
Hi,
I'm currently working on a project to help the analysis of malware from inside the kernel to avoid any kind of detection.
So I need to be able to read the process memory from my kernel module.
As of now, I'm stuck at converting a virtual memory address (for example 0x080483e8 found... (3 Replies)
If an executalbe file has several parameters, gdb can not pass parameters correctly. Let us see:
run:
./executablefile1 agr1 arg2 arg3
debug:
gdb executablefile1
run executalbefile1 arg1 arg2 arg3
then argv : executablefile1
argv : executablefile
argv : arg1
... (3 Replies)
I created one file (test.cpp)and complied it and get the executable file(test) and run it.It is giving the out put but when I am trying to debug that executable.I am getting the error --
please tell me the solutions??
Thanks in advance ..... (2 Replies)
Hi,
I am not able to access wi-fi network from my laptop HP-DV6-1111au. Please suggest how can i load a driver for the device and set the network right!! (3 Replies)
Hello,
I am using CentOS 5.8 x64 server for our one of internal application which is developed on PHP and Mysql as DB.
Currently there are 8-10 instances deployed on this server some of them are rarely used.
Below is the H/W specification fort the same :-
Procesor :- Intel(R) Xeon(R) CPU ... (6 Replies)
Hi,
i have just installed 4 gb RAM ddr3 on OS Windows 7 32 bit.
In "manage peripherals" i see this section:
Memory installed (ram) : 4,00 gb (2,30gb usable)
Why only 2,30 gb usable ?
In Windows 7 32bit the maximum size is not 3,00gb ?
see file attached, please (4 Replies)
Hello
I have built our application on AIX 7.1 as a 64 bit application.
My queries are as follows:
Can a 32bit gdb (v7.6) and ddd (data display debugger - v3.3.12), debug a 64bit executable ?
If I have a small 64bit a.exe executable that seems to work.
If I have a more complicated executable... (4 Replies)
Discussion started by: biju64
4 Replies
LEARN ABOUT LINUX
gzexe
GZEXE(1) General Commands Manual GZEXE(1)NAME
gzexe - compress executable files in place
SYNOPSIS
gzexe name ...
DESCRIPTION
The gzexe utility allows you to compress executables in place and have them automatically uncompress and execute when you run them (at a
penalty in performance). For example if you execute ``gzexe /usr/bin/gdb'' it will create the following two files:
-rwxr-xr-x 1 root root 1026675 Jun 7 13:53 /usr/bin/gdb
-rwxr-xr-x 1 root root 2304524 May 30 13:02 /usr/bin/gdb~
/usr/bin/gdb~ is the original file and /usr/bin/gdb is the self-uncompressing executable file. You can remove /usr/bin/gdb~ once you are
sure that /usr/bin/gdb works properly.
This utility is most useful on systems with very small disks.
OPTIONS -d Decompress the given executables instead of compressing them.
SEE ALSO gzip(1), znew(1), zmore(1), zcmp(1), zforce(1)CAVEATS
The compressed executable is a shell script. This may create some security holes. In particular, the compressed executable relies on the
PATH environment variable to find gzip and some standard utilities (basename, chmod, ln, mkdir, mktemp, rm, sleep, and tail).
BUGS
gzexe attempts to retain the original file attributes on the compressed executable, but you may have to fix them manually in some cases,
using chmod or chown.
GZEXE(1)
09-08-2014
