aboutsummaryrefslogtreecommitdiff
path: root/src/third_party/libdisasm/swig/README
diff options
context:
space:
mode:
authorLars Volker <lv@cloudera.com>2016-05-24 11:49:35 -0700
committerIvan Penkov <ivanpe@chromium.org>2016-05-24 11:49:35 -0700
commitf25a4112004efca7065068e87155757ef821d1e9 (patch)
tree5f6a4526979c4003709da7f74a9ad4f7f0efba63 /src/third_party/libdisasm/swig/README
parentFunctions only called by DumpFreeSpace need to be conditionally compiled. (diff)
downloadbreakpad-f25a4112004efca7065068e87155757ef821d1e9.tar.xz
Fix stack collection with size limit
src/client/linux/minidump_writer/minidump_writer.cc:273 obtains the stack info by calling GetStackInfo(). That method will return the stack base address, aligned to the bottom of the memory page that 'stack_pointer' is in. After that it will cap the size of the memory area to be copied into the minidump to 'max_stack_len', starting from the base address, if the caller requested so. This will be the case when collecting reduced stacks, as introduced by this change: https://breakpad.appspot.com/487002/ In such cases the caller will request 2048 bytes of memory. However GetStackInfo() will have aligned the base address to the page boundary, by default 4096 bytes. If the stack, which grows towards the base address from the top ends before the 2048 bytes of the first block, then we will not collect any useful part of the stack. As a fix we skip chunks of 'max_stack_len' bytes starting from the base address until the stack_pointer is actually contained in the chunk, which we will add to the minidump file. BUG=https://bugs.chromium.org/p/google-breakpad/issues/detail?id=695 R=ivanpe@chromium.org Review URL: https://codereview.chromium.org/1959643004 . Patch from Lars Volker <lv@cloudera.com>.
Diffstat (limited to 'src/third_party/libdisasm/swig/README')
0 files changed, 0 insertions, 0 deletions