From: "stigano at 163 dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/15870] New: backtrace don't give same result when called between redhat-32bit and redhat-64bit
Date: Wed, 21 Aug 2013 03:05:00 -0000 [thread overview]
Message-ID: <bug-15870-716@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=15870
Bug ID: 15870
Summary: backtrace don't give same result when called between
redhat-32bit and redhat-64bit
Product: glibc
Version: 2.18
Status: NEW
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: stigano at 163 dot com
CC: libc-locales at sourceware dot org
code:
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <signal.h>
#include <execinfo.h>
#include <fcntl.h>
#include <unistd.h>
void coredump_handle(int sig)
{
void *arraypoint[100];
size_t size;
size = backtrace(arraypoint,100);
return;
}
void core()
{
int i,j;
i=0,j=1;
printf("j/i=[%d]\n",j/i);
}
void test()
{
core();
}
void core_test()
{
test();
int a,b;
a=1,b=2;
a= b;
}
int main()
{
int i,j;
signal(SIGFPE,coredump_handle);
core_test();
i=0,j=1;
i++;
return 0;
}
this code run on redhat 32it cannot locate the line where cause coredump,only
locate the line the function called,but on redhat 64-bit do locate the line
cause coredump.
in functon coredump_handle,if the result of size is n on the 32-bit os,the
result of size always to be n-1.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2013-08-21 3:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 3:05 stigano at 163 dot com [this message]
2013-08-21 3:05 ` [Bug localedata/15870] " stigano at 163 dot com
2013-10-14 10:12 ` neleai at seznam dot cz
2014-06-13 13:17 ` fweimer at redhat dot com
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=bug-15870-716@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).