From: "Pereira, D LailaX E" <d.lailax.e.pereira@intel.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] correct seg fault address on ia-64??
Date: Wed, 14 Nov 2001 16:03:57 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805506@msgid-missing> (raw)
Hi ,
In the following program, I was trying to obtain the address where a
segmentation fault is caused.
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <signal.h>
#include <sys/mman.h>
int *x;
int page_size;
void segv_handler( int sig, siginfo_t *sip,struct sigcontext *scp){
void *vadr=sip->si_addr;
unsigned long *pc;
unsigned long instr;
int readwrite;
if (sig=SIGSEGV){
printf("\nSegv handler ..\n");
}
printf("vaddr : %x \n",vadr);
readwrite=(((*(unsigned long*)scp->sc_ip)>>21)&1);
printf("Read or write %d\n",readwrite);
exit(1);
}
int main(){
int s;
struct sigaction sa;
int temp;
page_size=getpagesize();
printf("Pagesize : %d ,PID=%d\n",page_size,(int)getpid());
fflush(stdout);
/*SEGV handler setup*/
sa.sa_handler=(void*)&segv_handler;
sigemptyset(&sa.sa_mask);
sigaddset(&sa.sa_mask,SIGIO);
sigaddset(&sa.sa_mask,SIGALRM);
sa.sa_flags=SA_SIGINFO;
if (sigaction(SIGSEGV,&sa,NULL)){
printf(" Error assigning signal!\n");
}
x=(int*)malloc(2*page_size);
/* Align to a multiple of page_size, assumed to be a power of two */
x = (int *)((long)(((int) (long)x + page_size-1) & ~(page_size-1)));
printf("Address: %x\n",x );
//x[0]E6;
s=mprotect(x,page_size,PROT_NONE); //make it none access
printf("Page protection : NONE : try reading the page\n ");
printf("segv should arise now ...\n");
//read the page ... segv?
temp=x[0];
return 0;
}
When I run the program on a ia-64 machine (linux OS) , then I get the
following output:
Pagesize : 16384 ,PID(513
Address: 4000
Page protection : NONE : try reading the page
segv should arise now ...
Segv handler ..
vaddr : 4000
Read or write 0
.............
However , when I ran the program thru gdb, I got the following:
Reading symbols from a.out...done.
(gdb) run ex3.c
......
Pagesize : 16384 ,PID(471
Address: 4000
Page protection : NONE : try reading the page
segv should arise now ...
Program received signal SIGSEGV, Segmentation fault.
0x40000000000010e0 in main ()
(gdb) where
#0 0x40000000000010e0 in main ()
#1 0x20000000000906b0 in __libc_start_main (
main=0x40000000000013e8 <_fini+408>, argc=2,
ubp_av=0x80000fffffffb848,
init=0x40000000000013b8 <_fini+360>,
fini=0x200000000003db30 <_dl_debug_mask>,
rtld_fini=0x20000000002581c8 <_dl_get_origin+632>,
stack_end=0x80000fffffffb840) at ../sysdeps/generic/libc-start.c:129
#2 0x40000000000010b0 in main ()
(gdb)....
So thru, gdb the seg fault address is "0x40000000000010e0" , is my
interpretation right ??
Why is that when I run the program on itanium , I get the address as "4000"
and thru gdb as " 0x40000000000010e0". What is wrong?? Please let me know.
d'laila
next reply other threads:[~2001-11-14 16:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-14 16:03 Pereira, D LailaX E [this message]
2001-11-14 16:42 ` [Linux-ia64] correct seg fault address on ia-64?? n0ano
2001-11-14 16:45 ` Andreas Schwab
2001-11-14 16:49 ` Dan Pop
2001-11-14 17:22 ` Rich Altmaier
2001-11-14 17:49 ` Christoph Hellwig
2001-11-14 18:02 ` n0ano
2001-11-14 18:51 ` Rok Sosic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590698805506@msgid-missing \
--to=d.lailax.e.pereira@intel.com \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.