public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "charlet at adacore dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/35284] Branch to 0x0 from Ada run-time
Date: Fri, 22 Feb 2008 08:35:00 -0000	[thread overview]
Message-ID: <20080222083444.21262.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35284-296@http.gcc.gnu.org/bugzilla/>



------- Comment #10 from charlet at adacore dot com  2008-02-22 08:34 -------
Subject: Re:  Branch to 0x0 from Ada run-time

> Arnaud, do you have any idea on what to look at (interesting breakpoint and
> data structures)? RTEMS tasking works on other platforms. May be some Ada/C
> thread interface data structure has the wrong size in the case of x86 and
> things get corrupted (s-oisinte-rtems.ads).

I'd suggest putting a watchpoint on the softlink that gets cleared to 0x0 (or
never set ?), you should see pretty quickly what's happening.

Note that I removed myself from cc: because I already receive all bugzilla
messages related to Ada PRs, so being in cc: means I receive the
messages twice, which is annoying given the amount of email I have
to deal with. It does not mean I'm ignoring this PR :-)

Arno


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35284


  parent reply	other threads:[~2008-02-22  8:35 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21 22:09 [Bug ada/35284] New: " joel at gcc dot gnu dot org
2008-02-21 22:11 ` [Bug ada/35284] " joel at gcc dot gnu dot org
2008-02-21 22:12 ` joel at gcc dot gnu dot org
2008-02-21 22:33 ` laurent at guerby dot net
2008-02-21 22:53 ` joel at gcc dot gnu dot org
2008-02-21 22:54 ` joel at gcc dot gnu dot org
2008-02-21 23:00 ` laurent at guerby dot net
2008-02-21 23:56 ` joel dot sherrill at oarcorp dot com
2008-02-22  8:03 ` charlet at gcc dot gnu dot org
2008-02-22  8:30 ` laurent at guerby dot net
2008-02-22  8:34   ` Arnaud Charlet
2008-02-22  8:35 ` charlet at adacore dot com [this message]
2008-02-22 15:35 ` joel at gcc dot gnu dot org
2008-02-22 16:44 ` joel at gcc dot gnu dot org
2008-02-22 20:54 ` joel at gcc dot gnu dot org
2008-02-22 21:13 ` laurent at guerby dot net
2008-02-22 21:56 ` joel at gcc dot gnu dot org
2008-02-22 22:02 ` joel at gcc dot gnu dot org
2008-02-22 22:03 ` laurent at guerby dot net
2008-02-22 22:36 ` joel at gcc dot gnu dot org
2008-02-25 20:46 ` joel at gcc dot gnu dot org
2008-03-14 21:47 ` joel at gcc dot gnu dot org
2008-03-14 22:30 ` laurent at guerby dot net
2008-03-31 20:17 ` joel at gcc dot gnu dot org
2008-03-31 20:22 ` laurent at guerby dot net
2008-04-01 18:02 ` joel at gcc dot gnu dot org
2008-04-01 19:41 ` laurent at guerby dot net
2008-04-01 22:40 ` joel at gcc dot gnu dot org
2008-04-02  7:37 ` laurent at guerby dot net
2008-04-02 11:45 ` laurent at guerby dot net
2008-04-02 15:09 ` joel at gcc dot gnu dot org
2008-04-02 16:45 ` laurent at guerby dot net
2008-04-03  0:11 ` joel at gcc dot gnu dot org
2008-04-03  0:15 ` joel at gcc dot gnu dot org
2008-04-03  3:46 ` laurent at guerby dot net
2008-04-03  3:48 ` laurent at guerby dot net
2008-04-03 14:31 ` joel dot sherrill at oarcorp dot com
2008-04-04 14:30 ` joel at gcc dot gnu dot org
2008-04-04 15:11 ` joel at gcc dot gnu dot org
2008-04-05  9:51 ` laurent at guerby dot net
2008-05-12 22:43 ` charlet at gcc dot gnu dot org

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=20080222083444.21262.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).