On Thu, Jan 26, 2017 at 8:48 AM, Dario Lombardo
wrote:
> On Thu, Jan 26, 2017 at 2:11 PM, Evan Huus wrote:
>> - your code will fail any time wmem chooses a different allocator
>> (this happens in CI, and occasionally elsewhere as well)
>>
>
> I
Hi again,
Can somebody point to me any simple example? I am able to tap the dissector
but I would like to write now a simple app that prints a message in the
terminal every time the packet() function is called. I know this looks
simple, but it's been some time and I can't get this running...
On Thu, Jan 26, 2017 at 3:41 PM, Jeff Morriss
wrote:
>
> Or are you looking for a way to make the crash easier to debug?
>
>
Yes. Basically I'd like the idea to give the user a very useful error
message. The wmem is pretty hard to debug, since a wrong scope basically
On Thu, Jan 26, 2017 at 8:48 AM, Dario Lombardo wrote:
> On Thu, Jan 26, 2017 at 2:11 PM, Evan Huus wrote:
>
>> What problem specifically are you trying to solve? There may be an easier
>> way.
>>
>> Evan
>
>
> The general problem is: a function
On Thu, Jan 26, 2017 at 2:11 PM, Evan Huus wrote:
>
> Each block can consist of multiple chunks, so you need a second, inner
> loop. You can do this with WMEM_CHUNK_NEXT.
>
> Do note, however, that:
> - you'll be iterating over every piece of memory allocated in this
> scope,
On Thu, Jan 26, 2017 at 4:06 AM, Dario Lombardo
wrote:
>
>
> On Wed, Jan 25, 2017 at 6:50 PM, Evan Huus wrote:
>>
>> On my phone, but the short version is that there's no way to check this,
>> and no efficient way to build it.
>>
>> Evan
>>
>
>
On Wed, Jan 25, 2017 at 6:50 PM, Evan Huus wrote:
> On my phone, but the short version is that there's no way to check this,
> and no efficient way to build it.
>
> Evan
>
>
Looking into the code it seems to me that the routine of free_all should
traverse all the allocated