Mailinglist Archive: opensuse-bugs (8120 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=248719


dcb314@xxxxxxxxxxx changed:

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




------- Comment #2 from dcb314@xxxxxxxxxxx  2007-02-27 13:38 MST -------
(In reply to comment #1)
> this is by design, the "invalid" access is always inside a memory page with
> valid objects, so it never causes a segfault.
> 
> please reopen if it in fact does cause problems.

>From the valgrind report, it looks to me like memory
is read after it has been freed.

I think I am correct to say that it is a C FAQ
to read or write memory after it has been freed.

See http://c-faq.com/malloc/useafterfree.html

There are other ways for a program to fail than
a segfault.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.