[Bug go/54749] New: libbacktrace

[Bug go/54749] New: libbacktrace

[Joost.VandeVondele at mat dot ethz.ch]

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

             Bug #: 54749
           Summary: libbacktrace
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: go
        AssignedTo: ian@airs.com
        ReportedBy: Joost.VandeVondele@mat.ethz.ch


On a testcase that makes the compiler run out-of-memory (by setting ulimit to 
ulimit -m 8388608
ulimit -v 8388608
ulimit -d 8388608
ulimit -t 600
and running the full testcase of PR53852) I get the following stacktrace, which
is a bit ugly:

GNU MP: Cannot allocate memory (size=8)
In function 'build_d_tensor_gks':
H�D$\x10A��\x01H�\x03H�D$\x18H�H�D$
H�C\x10H�D$(H�k\x10H�C\x18v,H��H�l$HH�\$@L�d$PL�l$XL�t$`H��h\x1f�Aborted
mmap: Cannot allocate memory
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
failed to read executable information
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make[2]: *** [semi_empirical_int_gks.o] Error 1
make[2]: Target `_progr' not remade because of errors.
make[2]: Leaving directory
`/data/vjoost/gnu/cp2k/cp2k/obj/gfortran-test12/sopt'
make[1]: *** [build] Error 2
make[1]: Leaving directory `/data/vjoost/gnu/cp2k/cp2k/makefiles'

[Bug go/54749] libbacktrace

[ian at airs dot com]

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

--- Comment #1 from Ian Lance Taylor <ian at airs dot com> 2012-09-29 16:59:02 UTC ---
You filed this against the "go" component, but it seems that Go is not
involved.  Is that right?  This is just about a backtrace printed after a run
of the Fortran compiler?

[Bug middle-end/54749] libbacktrace

[Joost.VandeVondele at mat dot ethz.ch]

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

--- Comment #2 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> 2012-09-29 17:34:04 UTC ---
(In reply to comment #1)
> You filed this against the "go" component, but it seems that Go is not
> involved.  Is that right?  This is just about a backtrace printed after a run
> of the Fortran compiler?

yes, unclear what the proper component was for libbacktrace... I didn't
consider this middle end either (and I was under the impression that go and
libbracktrace had something in common). 

The problem is not the fact that this particular run crashes, but the fact that
the trace should deal with the mmap out-of-mem more nicel (i.e. one line of
error).

[Bug other/54749] libbacktrace

[ian at airs dot com]

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

Ian Lance Taylor <ian at airs dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|middle-end                  |other

--- Comment #3 from Ian Lance Taylor <ian at airs dot com> 2012-09-29 17:48:25 UTC ---
The only connection between libbacktrace and go is that libgo uses
libbacktrace.

[Bug other/54749] libbacktrace

[ian at gcc dot gnu.org]

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

--- Comment #4 from ian at gcc dot gnu.org <ian at gcc dot gnu.org> 2012-09-29 17:51:01 UTC ---
Author: ian
Date: Sat Sep 29 17:50:54 2012
New Revision: 191855

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=191855
Log:
    PR other/54749
    * fileline.c (fileline_initialize): Pass errnum as -1 when
    reporting that we could not read executable information after a
    previous failure.

Modified:
    trunk/libbacktrace/ChangeLog
    trunk/libbacktrace/fileline.c

[Bug other/54749] libbacktrace

[ian at airs dot com]

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

Ian Lance Taylor <ian at airs dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|---                         |4.8.0

--- Comment #5 from Ian Lance Taylor <ian at airs dot com> 2012-09-29 17:51:45 UTC ---
Fixed.  Thanks for reporting it.