Symbols for different process displayed in stack trace

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Verbose Omaha logging enabled.
2. Information logging for Chrome enabled.
3. Run Omaha unit test.
4. Clear all events.
5. Let new Chrome events be collected.

What is the expected output? What do you see instead?
Since I don't have Chrome symbols, I expect the symbols to be empty.
Instead, I see 3 lines that match the Omaha unit test executable.

What version of the product are you using? On what operating system?
0.6.5.0
XP SP3

Please provide any additional information below.
The three matching addresses were:
0x00403554
0x00403B45
0x004469AF

I assume but have not confirmed that these same addresses exist in both 
Chrome and the unit test.

Original issue reported on code.google.com by ddor...@google.com on 7 Jun 2010 at 7:11

[GoogleCodeExporter]

This sounds like a problem with the module cache 
[http://code.google.com/p/sawbuck/source/browse/trunk/sawbuck/sym_util/module_ca
che.cc]. 
The module cache keeps at the top level, a map from {pid,time} to the module 
state in the process at that time. There was a bug in the comparison for the 
key 
[http://code.google.com/p/sawbuck/source/browse/trunk/sawbuck/sym_util/module_ca
che.h#92] at one point, which caused this problem to show quite frequently. 
A review of that code, or additional unittests would be most appreciated.

Original comment by si...@google.com on 11 Jun 2010 at 12:47

[GoogleCodeExporter]

Original comment by siggi@chromium.org on 4 Mar 2011 at 7:39

• Added labels: Area-Sawbuck

[GoogleCodeExporter]

error 1612

Original comment by billk...@gmail.com on 1 Apr 2013 at 4:19

[GoogleCodeExporter]

error 1612

Original comment by billk...@gmail.com on 1 Apr 2013 at 4:19

[GoogleCodeExporter]

error in my email address

Original comment by herbbrad...@gmail.com on 14 Apr 2013 at 3:40