public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/13302] Putting a va_list in a struct causes seg fault
Date: Thu, 04 Dec 2003 15:15:00 -0000	[thread overview]
Message-ID: <20031204151520.31534.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031204133352.13302.stuart.menefy@st.com>


------- Additional Comments From bangerth at dealii dot org  2003-12-04 15:15 -------
I can't reproduce this with a more recent snapshot on x86 linux. 
Can you 
a) use with a recent CVS snapshot? 
b) say something whether this is sh specific, i.e. does it not 
   crash on x86 for you? 
 
W. 

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING


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


  parent reply	other threads:[~2003-12-04 15:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04 13:33 [Bug c++/13302] New: " stuart dot menefy at st dot com
2003-12-04 15:13 ` [Bug c++/13302] " bangerth at dealii dot org
2003-12-04 15:15 ` bangerth at dealii dot org [this message]
2003-12-04 16:44 ` [Bug target/13302] " pinskia at gcc dot gnu dot org
2003-12-04 19:20 ` stuart dot menefy at st dot com
2003-12-04 19:45 ` [Bug target/13302] [3.3/3.4 Regression] " pinskia at gcc dot gnu dot org
2003-12-05 13:57 ` amylaar at gcc dot gnu dot org
2003-12-05 15:48 ` cvs-commit at gcc dot gnu dot org
2003-12-05 15:56 ` cvs-commit at gcc dot gnu dot org
2003-12-05 15:58 ` amylaar 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=20031204151520.31534.qmail@sources.redhat.com \
    --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).