[Bug fortran/17237] bug in f-valprint.c

[Bug fortran/17237] bug in f-valprint.c

[sergiodj at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=17237

Sergio Durigan Junior <sergiodj at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sergiodj at redhat dot com
           Assignee|unassigned at sourceware dot org   |sergiodj at redhat dot com

--- Comment #1 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
This is a bug, indeed.  I have a patch for this, will post it soon.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug fortran/17237] bug in f-valprint.c

[sergiodj at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=17237

--- Comment #2 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
Proposed fix: https://sourceware.org/ml/gdb-patches/2014-09/msg00073.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug fortran/17237] bug in f-valprint.c

[cvs-commit at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=17237

--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".

The branch, master has been updated
       via  eb0b04635f2f57506ab4365b32a6fc0b62920d2f (commit)
      from  5ee44bfa6bdb8eaf7f30eccb4fbdc989cb9bb7ca (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=eb0b04635f2f57506ab4365b32a6fc0b62920d2f

commit eb0b04635f2f57506ab4365b32a6fc0b62920d2f
Author: Sergio Durigan Junior <sergiodj@redhat.com>
Date:   Thu Sep 4 10:28:31 2014 -0400

    Fix PR fortran/17237: bug in f-valprint.c

    This commit fixes the PR mentioned in $subject.  It is about a set but
    unused variable that refers to the output format of integer values
    printed in Fortran.

    This was probably a thinko (like most set-but-unused-vars), but it
    could cause an internal error depending on the scenario.  I am sending
    a testcase which triggers this error as well.

    gdb/ChangeLog:
    2014-09-04  Sergio Durigan Junior  <sergiodj@redhat.com>

        PR fortran/17237
        * f-valprint.c (f_val_print): Specify the correct print option to
        use when printing integer values.

    gdb/testsuite/ChangeLog:
    2014-09-04  Sergio Durigan Junior  <sergiodj@redhat.com>

        PR fortran/17237
        * gdb.fortran/print-formatted.exp: New file.
        * gdb.fortran/print-formatted.f90: Likewise.

-----------------------------------------------------------------------

Summary of changes:
 gdb/ChangeLog                                 |    6 ++++
 gdb/f-valprint.c                              |    2 +-
 gdb/testsuite/ChangeLog                       |    6 ++++
 gdb/testsuite/gdb.fortran/print-formatted.exp |   39 +++++++++++++++++++++++++
 gdb/testsuite/gdb.fortran/print-formatted.f90 |   20 +++++++++++++
 5 files changed, 72 insertions(+), 1 deletions(-)
 create mode 100644 gdb/testsuite/gdb.fortran/print-formatted.exp
 create mode 100644 gdb/testsuite/gdb.fortran/print-formatted.f90

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug fortran/17237] bug in f-valprint.c

[sergiodj at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=17237

Sergio Durigan Junior <sergiodj at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #4 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
Fixed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.