Wmem does not use canaries under normal operation, but if you choose
the strict allocator (which the fuzz script, among others, does
automatically) then that allocator will do fuzzing, scrubbing of freed
memory, etc.
On Wed, Feb 4, 2015 at 10:44 AM, Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> wrote:
> So I deleted the EMEMification page from the wiki but I'm not sure what to
> do with the Canary page:
>
> http://wiki.wireshark.org/Development/Canary
>
> It looks like wmem does use canaries (under some circumstances?) so maybe it
> shouldn't be deleted. But I'm not familiar enough with what wmem is doing
> to rewrite it either...
>
> On 02/04/15 10:04, Evan Huus wrote:
>>
>> Woohoo!
>>
>> On Wed, Feb 4, 2015 at 2:00 AM, Wireshark code review
>> <code-review-do-not-reply@xxxxxxxxxxxxx> wrote:
>>>
>>> URL:
>>> https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=7ced085550d030ea10525d650c8d5d8dc7c99684
>>> Submitter: Anders Broman (a.broman58@xxxxxxxxx)
>>> Changed: branch: master
>>> Repository: wireshark
>>>
>>> Commits:
>>>
>>> 7ced085 by Michael Mann (mmann78@xxxxxxxxxxxx):
>>>
>>> emem is dead! Long live wmem!
>
>
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
