public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/27354]  New: Memory leak in make_relative_prefix
@ 2006-04-28 22:31 jvdelisle at gcc dot gnu dot org
  2007-01-30 22:11 ` [Bug driver/27354] " tromey at gcc dot gnu dot org
  0 siblings, 1 reply; 3+ messages in thread
From: jvdelisle at gcc dot gnu dot org @ 2006-04-28 22:31 UTC (permalink / raw)
  To: gcc-bugs

Using valgrind:

 valgrind -v --leak-check=full gfc -v 

--snip--

==4758== 30 bytes in 1 blocks are definitely lost in loss record 1 of 6
==4758==    at 0x1B909222: malloc (vg_replace_malloc.c:130)
==4758==    by 0x805D708: make_relative_prefix (make-relative-prefix.c:361)
==4758==    by 0x804D36C: process_command (gcc.c:3370)
==4758==    by 0x805345B: main (gcc.c:6182)

--snip--


-- 
           Summary: Memory leak in make_relative_prefix
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jvdelisle at gcc dot gnu dot org
  GCC host triplet: i686-pc-linux-gnu


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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug driver/27354] Memory leak in make_relative_prefix
  2006-04-28 22:31 [Bug c/27354] New: Memory leak in make_relative_prefix jvdelisle at gcc dot gnu dot org
@ 2007-01-30 22:11 ` tromey at gcc dot gnu dot org
  0 siblings, 0 replies; 3+ messages in thread
From: tromey at gcc dot gnu dot org @ 2007-01-30 22:11 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #1 from tromey at gcc dot gnu dot org  2007-01-30 22:11 -------
with svn head, I don't have 'gfc' (just gfortran) and the error is
slightly different:

==13467== 474 bytes in 8 blocks are definitely lost in loss record 3 of 4
==13467==    at 0x40051F9: malloc (vg_replace_malloc.c:149)
==13467==    by 0x8068D71: xmalloc (xmalloc.c:147)
==13467==    by 0x8066AD4: concat (concat.c:159)
==13467==    by 0x804FC86: process_command (gcc.c:3992)
==13467==    by 0x80564B4: main (gcc.c:6199)


-- 

tromey at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at gcc dot gnu dot
                   |                            |org
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2007-01-30 22:11:00
               date|                            |


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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug driver/27354] Memory leak in make_relative_prefix
       [not found] <bug-27354-4@http.gcc.gnu.org/bugzilla/>
@ 2014-03-21 14:04 ` jvdelisle at gcc dot gnu.org
  0 siblings, 0 replies; 3+ messages in thread
From: jvdelisle at gcc dot gnu.org @ 2014-03-21 14:04 UTC (permalink / raw)
  To: gcc-bugs

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

Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:

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

--- Comment #2 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
No apparent interest for a long time.


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2014-03-21 14:04 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-04-28 22:31 [Bug c/27354] New: Memory leak in make_relative_prefix jvdelisle at gcc dot gnu dot org
2007-01-30 22:11 ` [Bug driver/27354] " tromey at gcc dot gnu dot org
     [not found] <bug-27354-4@http.gcc.gnu.org/bugzilla/>
2014-03-21 14:04 ` jvdelisle at gcc dot gnu.org

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).