diff options
| author | Evan Huus <eapache@gmail.com> | 2013-07-26 13:06:50 +0000 |
|---|---|---|
| committer | Evan Huus <eapache@gmail.com> | 2013-07-26 13:06:50 +0000 |
| commit | 828eae73ce47d1e1a1d9e883f1dd63e2fddd9a65 (patch) | |
| tree | dc7c7be7c426b3af1e6977c7d457378ec3716bc9 /doc/README.wmem | |
| parent | 53ddabfe2e051104576697b9e371fa0f6a355754 (diff) | |
| download | wireshark-828eae73ce47d1e1a1d9e883f1dd63e2fddd9a65.tar.gz | |
Document that pinfo-scoped memory is also needed for anything passed to
add_new_data_source().
svn path=/trunk/; revision=50911
Diffstat (limited to 'doc/README.wmem')
| -rw-r--r-- | doc/README.wmem | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/README.wmem b/doc/README.wmem index b779cf4351..24a838952b 100644 --- a/doc/README.wmem +++ b/doc/README.wmem @@ -59,13 +59,14 @@ NB: Using these pools outside of the appropriate scope (eg using the packet The epan pool is scoped to the library's lifetime - memory allocated in it is not freed until epan_cleanup() is called, which is typically at the end of the -program. +program. 2.1.2 Pinfo Pool -Certain places (such as AT_STRINGZ address allocations) need their memory to -stay around a little longer than the usual packet scope - basically until the -next packet is dissected. This is effectively the scope of Wireshark's pinfo +Certain allocations (such as AT_STRINGZ address allocations and anything that +might end up being passed to add_new_data_source) need their memory to stick +around a little longer than the usual packet scope - basically until the +next packet is dissected. This is, in fact, the scope of Wireshark's pinfo structure, so the pinfo struct has a 'pool' member which is a wmem pool scoped to the lifetime of the pinfo struct. |