Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "François Chenais" <francois@chenais.net>
To: gdb@sourceware.org
Subject: [OPTERON/x86_64] - can debug while setting breakpoint
Date: Thu, 05 Feb 2009 18:49:00 -0000	[thread overview]
Message-ID: <498B34A4.8030607@chenais.net> (raw)

Hello,

Something strange happens while trying to debug on x86_64 system.

I have a simple C code in t.c file ...

     #include <stdio.h>
      void main (int argc, char **argv) { printf("Hello World !"\n); }
 
... built with ...

    # gcc -g t.c

... and run it

    # a.out
    Hello World !

ldd is ok

    libc.so.6 => /lib64/libc.so.6 (0x000000304f200000)
    /lib64/ld-linux-x86-64.so.2 (0x000000304da00000)


Now running it with gdb :

    # gdb a.out
    blah blah blah
    (gdb) run
    Starting program: /home/francois/src/a.out
    Hello World !

    Program exited with code 016.
    (gdb)  b main
    Breakpoint 1 at 0x80483b5: file t.c, line 2.

    (gdb) run


At this moment, a  SIGSEGV occurs before stopping on the breakpoint !!!
The stack is buggy !


More informations that can help
=====================

The same error occurs with others debuggers : totalview, sun dbx, intel idb
and while using  intel icc or  g++ compilers  :/

The same error occurs while building with -static option.

I've done the test on 5 Amd opteron x86_64 hosts with Cent OS 5.2
     - The error occurs on 3/5.



Any idea ???

    Thanks a lot by advance

            François







  








             reply	other threads:[~2009-02-05 18:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-05 18:49 François Chenais [this message]
2009-02-05 18:57 ` Daniel Jacobowitz
2009-02-05 19:16   ` [OPTERON/x86_64] - can't " François Chenais
2009-02-10  8:26     ` François Chenais
2009-02-20  9:03       ` François Chenais
2009-02-22 10:46 ` [OPTERON/x86_64] - can " Jan Kratochvil
2009-02-23  7:34   ` François Chenais

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=498B34A4.8030607@chenais.net \
    --to=francois@chenais.net \
    --cc=gdb@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