public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47296] I/O Segfault when running out of file descriptors
Date: Sat, 15 Jan 2011 09:18:00 -0000	[thread overview]
Message-ID: <bug-47296-4-2vrILNcmee@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47296-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> 2011-01-15 06:42:33 UTC ---
Author: jvdelisle
Date: Sat Jan 15 06:42:30 2011
New Revision: 168832

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=168832
Log:
2011-01-14  Jerry DeLisle  <jvdelisle@gcc.gnu.org>

    PR libgfortran/47296
    * io/unix.c (unpack_filename): Return non-zero if the filename passed
    in is NULL.

Modified:
    trunk/libgfortran/ChangeLog
    trunk/libgfortran/io/unix.c


  parent reply	other threads:[~2011-01-15  6:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14 16:48 [Bug fortran/47296] New: " burnus at gcc dot gnu.org
2011-01-14 20:01 ` [Bug fortran/47296] " burnus at gcc dot gnu.org
2011-01-14 20:01 ` jvdelisle at gcc dot gnu.org
2011-01-15  6:42 ` jvdelisle at gcc dot gnu.org
2011-01-15  9:18 ` jvdelisle at gcc dot gnu.org [this message]
2011-01-15 10:49 ` jb at gcc dot gnu.org
2011-01-15 15:23 ` jvdelisle at frontier dot com
2011-01-15 19:31 ` jvdelisle at gcc dot gnu.org
2011-01-15 21:50 ` jb at gcc dot gnu.org
2011-01-16  8:35 ` jvdelisle at gcc dot gnu.org
2011-01-16 20:15 ` jb at gcc dot gnu.org
2011-01-17  8:01 ` jvdelisle at gcc dot gnu.org
2011-01-22 15:55 ` jvdelisle at gcc dot gnu.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=bug-47296-4-2vrILNcmee@http.gcc.gnu.org/bugzilla/ \
    --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).