public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Prabha Suresh <Prabha.Venkatachalam@alcatel.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/5566: When we access the stream objects,it dumps core
Date: Mon, 04 Feb 2002 21:46:00 -0000	[thread overview]
Message-ID: <20020205054603.29151.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/5566; it has been noted by GNATS.

From: Prabha Suresh <Prabha.Venkatachalam@alcatel.com>
To: rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
        nobody@gcc.gnu.org, prabha.venkatachalam@alcatel.com,
        prabha_p_v@yahoo.com, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/5566: When we access the stream objects,it dumps core
Date: Tue, 05 Feb 2002 11:13:44 -0500

 --------------17040D6EB3B7446A69EC71C2
 Content-Type: text/plain; charset=us-ascii
 Content-Transfer-Encoding: 7bit
 
 I'll send you the traces,after execution
 The problem was with the stream objects,when we changed to a normal char buffer,it
 works fine.
 Thanks in Advance
 Prabha
 
 rodrigc@gcc.gnu.org wrote:
 
 > Synopsis: When we access the stream objects,it dumps core
 >
 > State-Changed-From-To: open->feedback
 > State-Changed-By: rodrigc
 > State-Changed-When: Mon Feb  4 09:16:02 2002
 > State-Changed-Why:
 >     You did not provide a complete testcase.
 >     See: http://gcc.gnu.org/bugs.html and provide preprocessed
 >     source.
 >
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5566
 
 --
 ************* Leadership is action,not the position *****************
 
 
 
 --------------17040D6EB3B7446A69EC71C2
 Content-Type: text/html; charset=us-ascii
 Content-Transfer-Encoding: 7bit
 
 <!doctype html public "-//w3c//dtd html 4.0 transitional//en">
 <html>
 I'll send you the traces,after execution
 <br>The problem was with the stream objects,when we changed to a normal
 char buffer,it works fine.
 <br>Thanks in Advance
 <br>Prabha
 <p>rodrigc@gcc.gnu.org wrote:
 <blockquote TYPE=CITE>Synopsis: When we access the stream objects,it dumps
 core
 <p>State-Changed-From-To: open->feedback
 <br>State-Changed-By: rodrigc
 <br>State-Changed-When: Mon Feb&nbsp; 4 09:16:02 2002
 <br>State-Changed-Why:
 <br>&nbsp;&nbsp;&nbsp; You did not provide a complete testcase.
 <br>&nbsp;&nbsp;&nbsp; See: <a href="http://gcc.gnu.org/bugs.html">http://gcc.gnu.org/bugs.html</a>
 and provide preprocessed
 <br>&nbsp;&nbsp;&nbsp; source.
 <p><a href="http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5566">http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&amp;database=gcc&amp;pr=5566</a></blockquote>
 
 <pre>--&nbsp;
 ************* Leadership is action,not the position *****************</pre>
 &nbsp;</html>
 
 --------------17040D6EB3B7446A69EC71C2--
 


             reply	other threads:[~2002-02-05  5:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-04 21:46 Prabha Suresh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-18 17:24 rodrigc
2002-02-04  9:16 rodrigc
2002-02-01  2:06 prabha.venkatachalam

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=20020205054603.29151.qmail@sources.redhat.com \
    --to=prabha.venkatachalam@alcatel.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).