I have upgraded my libc with gnumalloc() patch and now it is ok but what I
want to point out is how is a bus error generated in the 1st case on a 386
machine when the man page says otherwise.
And one more question: Do the later x86's generate this signal ?
I tried this program :-
main()
{
long l=1234;
char *c ;
int *i;
c=&l;
c++;
i=&l;
printf("%d\n",i);
printf("%d\n",*i);
i=(int *)c;
printf("%d\n",i);
printf("%d",*i);
}
As fas as my CS theory goes , bus error occurs when I try to access an int
on an odd location. This program dumps core with a bus error on HP-UX and
Solaris and not on Linux .
Any pointers would be greatly appreciated.
Also I would like to know , has anyone ever come across a program on Linux
which dumps core with a SIG_BUS other than netscape ??
--suman
I----------------------------------------------------------------------------I
I Suman Saraf http://oasis3.hss.hns.com/~suman. I
I Satellite Networking Division, PGP: finger suman@gabbar.svrec.ernet.in. I
I Thuraya-Mobilsat-OMC http://www.hughes-soft.com. I
I Hughes Software Systems,Plot 31, Sector 18 , Electronic City,Gurgaon. I
I Tel: 343703-08 Ext: 2423. I
I ---------------------------------------------------------------------------I
I Great operating systems have always encountered I
I violent opposition from mediocre minds. I
I --Anonymous I
I----------------------------------------------------------------------------I
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu