On 01/26/2012 05:54 PM, Ori Berger wrote:
On 01/26/2012 10:16 AM, Baruch Siach wrote:
Only by using valgrind, that I could find the exact location and figure
out, that it was another function that had the problem.
How does the modern memory management system is working then, that it
takes
so m
On Thu, Jan 26, 2012 at 18:08, Yedidyah Bar-David <
linux...@didi.bardavid.org> wrote:
> On Thu, Jan 26, 2012 at 10:54:56AM -0500, Ori Berger wrote:
> > On 01/26/2012 10:16 AM, Baruch Siach wrote:
> >
> > >>Only by using valgrind, that I could find the exact location and figure
> > >>out, that it
On Thu, Jan 26, 2012 at 10:54:56AM -0500, Ori Berger wrote:
> On 01/26/2012 10:16 AM, Baruch Siach wrote:
>
> >>Only by using valgrind, that I could find the exact location and figure
> >>out, that it was another function that had the problem.
> >>
> >>How does the modern memory management system
On 01/26/2012 10:16 AM, Baruch Siach wrote:
Only by using valgrind, that I could find the exact location and figure
out, that it was another function that had the problem.
How does the modern memory management system is working then, that it takes
so much time for the problem to surface ?
Now
Hi Ido,
On Thu, Jan 26, 2012 at 04:34:28PM +0200, ik wrote:
> In the past week I had several bugs that while gdb pointed to a place X,
> the actual place was several instructions prior to that position.
>
> For example the following error message I had to an off by one bug:
> *** glibc detected *
