public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: <gcc@gnu.org>, <gcc-help@gnu.org>
Subject: Seg fault in  call_gmon_start
Date: Fri, 07 Mar 2008 06:42:00 -0000	[thread overview]
Message-ID: <D2719086B82D7741A242696B378887AA04C8B252@NAEX11.na.qualcomm.com> (raw)

I just compiled an app with GCC. It is segmentation faulting in call_gmon_start (even before reaching main() of my program

What does call_gmon_start() do ? Which library defines this function? 

gdb) where
#0  0x2a000750 in call_gmon_start ()
#1  0x00000000 in ?? ()
(gdb) info


(gdb) disassemble call_gmon_start
Dump of assembler code for function call_gmon_start:
0x2a000750 <call_gmon_start+0>: str     r10, [sp, #-4]!
0x2a000754 <call_gmon_start+4>: ldr     r10, [pc, #32]  ; 0x2a00077c <call_gmon_start+44>
0x2a000758 <call_gmon_start+8>: ldr     r3, [pc, #32]   ; 0x2a000780 <call_gmon_start+48>
0x2a00075c <call_gmon_start+12>:        add     r10, pc, r10
0x2a000760 <call_gmon_start+16>:        ldr     r2, [r10, r3]
0x2a000764 <call_gmon_start+20>:        cmp     r2, #0  ; 0x0
0x2a000768 <call_gmon_start+24>:        beq     0x2a000774 <call_gmon_start+36>
0x2a00076c <call_gmon_start+28>:        ldmia   sp!, {r10}
0x2a000770 <call_gmon_start+32>:        b       0x2a000744 <_init+100>
0x2a000774 <call_gmon_start+36>:        ldmia   sp!, {r10}
0x2a000778 <call_gmon_start+40>:        bx      lr
0x2a00077c <call_gmon_start+44>:        andeq   r8, r0, r0, ror #9
0x2a000780 <call_gmon_start+48>:        andeq   r0, r0, r12, lsr #32
End of assembler dump.

             reply	other threads:[~2008-03-07  6:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07  6:42 Desineni, Harikishan [this message]
2008-03-08 23:11 ` Jim Wilson

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=D2719086B82D7741A242696B378887AA04C8B252@NAEX11.na.qualcomm.com \
    --to=hdesinen@qualcomm.com \
    --cc=gcc-help@gnu.org \
    --cc=gcc@gnu.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).