public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug fortran/11354] error in evaluating variable length fortran strings causes stalls
Date: Fri, 29 Apr 2011 17:03:00 -0000	[thread overview]
Message-ID: <bug-11354-4717-WlKkCUnf5e@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11354-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=11354

--- Comment #6 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2011-04-29 17:03:10 UTC ---
(In reply to comment #5)
> The below example actually reproduces the stalling behaviour

The problem is people sometimes print huge arrays for example into file and it
takes a lot of time.  There was discussed some way to read data while it is
being printed instead of reading it all in advance.  No limit is going to fit
all the cases.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2011-04-29 17:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11354-4717@http.sourceware.org/bugzilla/>
2011-04-29 13:48 ` jan.kratochvil at redhat dot com
2011-04-29 16:27 ` stephan.kramer at imperial dot ac.uk
2011-04-29 16:35 ` jan.kratochvil at redhat dot com
2011-04-29 16:59 ` stephan.kramer at imperial dot ac.uk
2011-04-29 17:03 ` jan.kratochvil at redhat dot com [this message]
2010-03-07 22:06 [Bug fortran/11354] New: " stephan dot kramer at imperial dot ac dot uk
2010-09-14 19:21 ` [Bug fortran/11354] " stephan dot kramer at imperial dot ac dot uk

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=bug-11354-4717-WlKkCUnf5e@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).