aboutsummaryrefslogtreecommitdiff
path: root/src/processor
diff options
context:
space:
mode:
authormkrebs@chromium.org <mkrebs@chromium.org@4c0a9323-5329-0410-9bdc-e9ce6186880e>2012-03-30 21:59:16 +0000
committermkrebs@chromium.org <mkrebs@chromium.org@4c0a9323-5329-0410-9bdc-e9ce6186880e>2012-03-30 21:59:16 +0000
commit70f5af9444d72049c10e5d2f93e06d8108059bf6 (patch)
tree79560f041b48aee3f752badbbe8d5f4271757bcf /src/processor
parentFix memory leak in DisassemblerX86. (diff)
downloadbreakpad-70f5af9444d72049c10e5d2f93e06d8108059bf6.tar.xz
Fix GetMainModule() to properly get first module
Change MinidumpModuleList::GetMainModule() to use GetModuleAtIndex() instead of GetModuleAtSequence() because the former gets the first module that was in the minidump file, while the latter actually gets the first module when sorted by address. While this is pretty much the same thing at the moment, I have another change in the works that can sometimes affect the module order in the file. BUG=chromium-os:25355 TEST=Ran Breakpad tests Review URL: https://breakpad.appspot.com/366001 git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@941 4c0a9323-5329-0410-9bdc-e9ce6186880e
Diffstat (limited to 'src/processor')
-rw-r--r--src/processor/minidump.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/processor/minidump.cc b/src/processor/minidump.cc
index 34ca7dce..3ca52ff7 100644
--- a/src/processor/minidump.cc
+++ b/src/processor/minidump.cc
@@ -2483,7 +2483,7 @@ const MinidumpModule* MinidumpModuleList::GetMainModule() const {
// The main code module is the first one present in a minidump file's
// MDRawModuleList.
- return GetModuleAtSequence(0);
+ return GetModuleAtIndex(0);
}