[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Minor patch to correct buffer overrun
From: |
Eli Zaretskii |
Subject: |
Re: Minor patch to correct buffer overrun |
Date: |
Tue, 17 Aug 2010 05:59:21 +0300 |
> Date: Mon, 16 Aug 2010 16:53:27 -0400
> From: Chris Sutcliffe <address@hidden>
> CC: address@hidden, address@hidden
>
> 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 I mentioned, as a result of the optimization debugging is
> problematic. Compiling without optimization works just fine.
Can you make it crash if you compile with -O1 instead of -O2? With
the -O1 switch, the backtrace should be more meaningful.
- 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, 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, 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