public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "opensource at artnaseef dot com" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/606] New: profiling causes segfault in gmon mcount on ARM
Date: Fri, 10 Dec 2004 20:51:00 -0000	[thread overview]
Message-ID: <20041210205058.606.opensource@artnaseef.com> (raw)

The gmon support for ARM often causes the profiled program to segfault in 
_monstartup() due to the allocation memory and setting of pointers; some times 
the p->froms pointer is assigned at an offset of 2 from a 4-byte boundary.

Due to the ARM CPU's odd handling of mis-aligned words, this leads to a 
segmentation fault.

The ARM CPU (at least in Little Endian Mode) handles mis-aligned accesses 
(offset 2 from a word boundary) by adjusting the address back to the immediately 
previous 4-byte boundary and swapping the low and high 2-byte words.

-- 
           Summary: profiling causes segfault in gmon mcount on ARM
           Product: glibc
           Version: 2.3.2
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: gotom at debian dot or dot jp
        ReportedBy: opensource at artnaseef dot com
                CC: glibc-bugs at sources dot redhat dot com,opensource at
                    artnaseef dot com
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: arm-linux
GCC target triplet: arm-linux


http://sources.redhat.com/bugzilla/show_bug.cgi?id=606

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2004-12-10 20:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-10 20:51 opensource at artnaseef dot com [this message]
2004-12-10 20:53 ` [Bug libc/606] " opensource at artnaseef dot com
2004-12-15 12:24 ` gotom at debian dot or dot jp
2005-10-10 14:53 ` drow at sources dot 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=20041210205058.606.opensource@artnaseef.com \
    --to=sourceware-bugzilla@sources.redhat.com \
    --cc=glibc-bugs@sources.redhat.com \
    /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).