[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Minor patch to correct buffer overrun
From: |
Chris Sutcliffe |
Subject: |
Re: Minor patch to correct buffer overrun |
Date: |
Wed, 18 Aug 2010 08:31:31 -0400 |
On 16 August 2010 16:53, Chris Sutcliffe wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x00403a03 in find_directory (name=<value optimized out>) at
> ../make-3.82/dir.c:537
> 537 else if (!strcmp(fs_type, "FAT"))
> (gdb) bt full
> #0 0x00403a03 in find_directory (name=<value optimized out>) at
> ../make-3.82/dir.c:537
> dc = Cannot access memory at address 0x63726dcf
> (gdb)
As previously stated, I'm no GDB expert, but does the fact that GDB
indicates that 'dc' could not access memory mean that the issue is
with 'dc' (which is a malloc)?
Chris
--
Chris Sutcliffe
http://emergedesktop.org
http://www.google.com/profiles/ir0nh34d
- Minor patch to correct buffer overrun, Chris Sutcliffe, 2010/08/16
- Re: Minor patch to correct buffer overrun, Paul Smith, 2010/08/16
- Re: Minor patch to correct buffer overrun, Chris Sutcliffe, 2010/08/16
- Re: Minor patch to correct buffer overrun,
Chris Sutcliffe <=
- Re: Minor patch to correct buffer overrun, Chris Sutcliffe, 2010/08/18
- Re: Minor patch to correct buffer overrun, Eli Zaretskii, 2010/08/18
- Re: Minor patch to correct buffer overrun, Paul Smith, 2010/08/18
- Re: Minor patch to correct buffer overrun, Eli Zaretskii, 2010/08/18
- Re: Minor patch to correct buffer overrun, Eli Zaretskii, 2010/08/18
- Re: Minor patch to correct buffer overrun, Chris Sutcliffe, 2010/08/18
- Re: Minor patch to correct buffer overrun, Eli Zaretskii, 2010/08/18
- Re: Minor patch to correct buffer overrun, Chris Sutcliffe, 2010/08/18
- Re: Minor patch to correct buffer overrun, Eli Zaretskii, 2010/08/19
- Re: Minor patch to correct buffer overrun, Chris Sutcliffe, 2010/08/19