bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug admin/10785] New: memory access violation in bfd/opncls.c


From: jerker dot back at gmail dot com
Subject: [Bug admin/10785] New: memory access violation in bfd/opncls.c
Date: 15 Oct 2009 23:19:01 -0000

I get a memory access violation when running a 64-bit debug build of binutils 
current nm on x86_64 Interix. Like this:
nm-new /usr/lib/somelib

The shell print some lines and then become unresponsive

shell: Interix 64bit ksh (pdksh)
Compiler: Interix cc frontend of MS x64 compiler 15.00.30729.01

Running a 32bit Interix gcc 3.3 nm binary build will exit silently at same spot

The offending line is:
bfd/opncls.c(712): free (bim->buffer);
in this code block
-----------------------------------------------------------------------------  
if ((abfd->flags & BFD_IN_MEMORY) != 0)
    {
      /* FIXME: cagney/2004-02-15: Need to implement a BFD_IN_MEMORY io
         vector.
         Until that's done, at least don't leak memory.  */
      struct bfd_in_memory *bim = (struct bfd_in_memory *) abfd->iostream;
      free (bim->buffer);
      free (bim);
      ret = TRUE;
    }
  else
    ret = abfd->iovec->bclose (abfd);

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

Note that free should work even if there are no memory allocated

-- 
           Summary: memory access violation in bfd/opncls.c
           Product: binutils
           Version: 2.21 (HEAD)
            Status: NEW
          Severity: critical
          Priority: P2
         Component: admin
        AssignedTo: unassigned at sources dot redhat dot com
        ReportedBy: jerker dot back at gmail dot com
                CC: bug-binutils at gnu dot org
 GCC build triplet: x86_64-unknown-interix6.1
  GCC host triplet: x86_64-unknown-interix6.1
GCC target triplet: x86_64-unknown-interix6.1


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]