NetworkSourceLineResolverServer.SystemTest fails on Linux

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run src/processor/network_source_line_resolver_server_unittest

What is the expected output? What do you see instead?

Expected: passing test
Actual: failing test / crashing?

I tested on 64-bit Hardy and Lucid.

With r569 on Hardy, I get:

src/processor/network_source_line_resolver_server_unittest
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from NetworkSourceLineResolverServer
[ RUN      ] NetworkSourceLineResolverServer.SystemTest
2010-11-08 12:25:58: udp_network.cc:108: INFO: Listening on address 127.0.0.1
2010-11-08 12:25:58: udp_network.cc:125: INFO: Listening on port 54274
2010-11-08 12:25:58: udp_network.cc:77: INFO: Initializing network connection 
to localhost:54274
2010-11-08 12:25:58: minidump_processor.cc:238: INFO: Processing minidump in 
file ./src/processor/testdata/minidump2.dmp
2010-11-08 12:25:58: minidump.cc:3494: INFO: Minidump opened minidump 
./src/processor/testdata/minidump2.dmp
2010-11-08 12:25:58: minidump.cc:3539: INFO: Minidump not byte-swapping minidump
2010-11-08 12:25:58: minidump.cc:3896: INFO: GetStream: type 1197932546 not 
present
2010-11-08 12:25:58: minidump.cc:1942: INFO: MinidumpModule could not determine 
version for c:\test_app.exe
2010-11-08 12:25:58: minidump_processor.cc:106: INFO: Minidump 
./src/processor/testdata/minidump2.dmp has CPU info, OS info, Breakpad info, 
exception, module list, thread list, dump thread, and requesting thread
2010-11-08 12:25:58: minidump_processor.cc:140: INFO: Looking at thread 
./src/processor/testdata/minidump2.dmp:0/2 id 0xbf4
2010-11-08 12:25:58: network_source_line_resolver.cc:342: INFO: Sending 72 bytes
2010-11-08 12:25:58: network_source_line_server.cc:151: INFO: Received message 
HAS c:\test_app.exe c:\test_app.pdb 5A9832E5287241C1838ED98914E9B7FF1
2010-11-08 12:25:58: network_source_line_resolver.cc:356: INFO: received 4 bytes
2010-11-08 12:25:58: network_source_line_resolver.cc:342: INFO: Sending 72 bytes
2010-11-08 12:25:58: network_source_line_server.cc:179: INFO: Received message 
LOAD c:\test_app.exe c:\test_app.pdb 5A9832E5287241C1838ED98914E9B7FF1
2010-11-08 12:25:58: network_source_line_server.cc:194: INFO: Looking up 
symbols for (c:\test_app.exe, c:\test_app.pdb, 
5A9832E5287241C1838ED98914E9B7FF1)
2010-11-08 12:25:58: network_source_line_server.cc:207: INFO: Found symbols for 
c:\test_app.exe
2010-11-08 12:25:58: basic_source_line_resolver.cc:245: INFO: Loading symbols 
for module c:\test_app.exe|c:\test_app.pdb|5A9832E5287241C1838ED98914E9B7FF1 
from buffer
2010-11-08 12:25:58: network_source_line_server.cc:223: INFO: Loaded symbols 
for c:\test_app.exe (22151 lines, 22151 total)
2010-11-08 12:25:58: network_source_line_resolver.cc:356: INFO: received 4 bytes
2010-11-08 12:25:58: network_source_line_resolver.cc:342: INFO: Sending 88 bytes
2010-11-08 12:25:58: network_source_line_server.cc:262: INFO: Received message 
GET c:\test_app.exe c:\test_app.pdb 5A9832E5287241C1838ED98914E9B7FF1 400000 
40429e
2010-11-08 12:25:58: network_source_line_server.cc:118: INFO: Sending GET 
response: `anonymous namespace'::CrashFunction 404290 c:\test_app.cc 58 40429b
2010-11-08 12:25:58: network_source_line_resolver.cc:356: INFO: received 77 
bytes
2010-11-08 12:25:58: network_source_line_resolver.cc:172: INFO: GET response: 
`anonymous namespace'::CrashFunction 404290 c:\test_app.cc 58 40429b
2010-11-08 12:25:58: network_source_line_resolver.cc:156: INFO: Sending 58 bytes
2010-11-08 12:25:58: network_source_line_server.cc:12b: INFO: Received message 
GETSTACKWIN c:\test_app.exe c:\test_app.pdb 5A9832E5287241C1838ED98914E9B7FF1 
400000 40429e
2010-11-08 12:26:03: network_source_line_resolver.cc:156: INFO: Sending 58 bytes
2010-11-08 12:26:08: network_source_line_resolver.cc:156: INFO: Sending 58 bytes
2010-11-08 12:26:13: network_source_line_resolver.cc:156: INFO: Sending 58 bytes
2010-11-08 12:26:18: network_source_line_resolver.cc:156: INFO: Sending 58 bytes
2010-11-08 12:26:23: network_source_line_resolver.cc:156: INFO: Sending 58 bytes
2010-11-08 12:26:28: network_source_line_resolver.cc:156: INFO: Sending 58 bytes
2010-11-08 12:26:33: network_source_line_resolver.cc:156: INFO: Sending 58 bytes
2010-11-08 12:26:38: network_source_line_resolver.cc:156: INFO: Sending 56 bytes
2010-11-08 12:26:43: network_source_line_resolver.cc:156: INFO: Sending 56 bytes
2010-11-08 12:26:48: minidump_processor.cc:8c: INFO: Looking at thread 
./src/processor/testdata/minidump2.dmp:1/2 id 0x11c0
2010-11-08 12:26:48: minidump_processor.cc:e8: INFO: Processed 
./src/processor/testdata/minidump2.dmp
2010-11-08 12:26:48: minidump.cc:d8a: INFO: Minidump closing minidump
src/processor/network_source_line_resolver_server_unittest.cc:164: Failure
Value of: "main"
Expected: stack->frames()->at(1)->function_name
Which is: ""
[  FAILED  ] NetworkSourceLineResolverServer.SystemTest (50021 ms)
[----------] 1 test from NetworkSourceLineResolverServer (50021 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (50021 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] NetworkSourceLineResolverServer.SystemTest

 1 FAILED TEST

Note: In many of the ASSERT_EQ(expected, actual) statements, expected and 
actual are backwards.

At r729, on my Hardy machine, I get:

src/processor/network_source_line_resolver_server_unittest
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from NetworkSourceLineResolverServer
[ RUN      ] NetworkSourceLineResolverServer.SystemTest
2010-11-08 12:30:07: udp_network.cc:110: INFO: Listening on address 127.0.0.1
2010-11-08 12:30:07: udp_network.cc:127: INFO: Listening on port 60640
2010-11-08 12:30:07: udp_network.cc:79: INFO: Initializing network connection 
to localhost:60640
2010-11-08 12:30:07: minidump_processor.cc:264: INFO: Processing minidump in 
file ./src/processor/testdata/minidump2.dmp
2010-11-08 12:30:07: minidump.cc:3500: INFO: Minidump opened minidump 
./src/processor/testdata/minidump2.dmp
2010-11-08 12:30:07: minidump.cc:3545: INFO: Minidump not byte-swapping minidump
2010-11-08 12:30:07: minidump.cc:3902: INFO: GetStream: type 1197932546 not 
present
2010-11-08 12:30:07: minidump.cc:1945: INFO: MinidumpModule could not determine 
version for c:\test_app.exe
2010-11-08 12:30:07: minidump_processor.cc:116: INFO: Minidump 
./src/processor/testdata/minidump2.dmp has CPU info, OS info, Breakpad info, 
exception, module list, thread list, dump thread, and requesting thread
2010-11-08 12:30:07: minidump_processor.cc:150: INFO: Looking at thread 
./src/processor/testdata/minidump2.dmp:0/2 id 0xbf4
2010-11-08 12:30:07: network_source_line_resolver.cc:362: INFO: Sending 72 bytes
2010-11-08 12:30:07: network_source_line_server.cc:151: INFO: Received message 
HAS c:\test_app.exe c:\test_app.pdb 5A9832E5287241C1838ED98914E9B7FF1
2010-11-08 12:30:07: network_source_line_resolver.cc:376: INFO: received 4 bytes
*** glibc detected *** 
src/processor/network_source_line_resolver_server_unittest: free(): invalid 
pointer: 0x00007fd101d849e0 ***

(backtrace doesn't have symbols)

Original issue reported on code.google.com by thestig@chromium.org on 8 Nov 2010 at 8:32

[GoogleCodeExporter]

Yeah, I'm not sure when this started failing, but I noticed it earlier and 
didn't have time to look into it. It used to pass on my 64-bit Ubuntu Karmic 
box, certainly.

Original comment by ted.mielczarek on 9 Nov 2010 at 3:27

[GoogleCodeExporter]

This now passes on my Ubuntu Karmic box, since the crash was fixed.

Original comment by ted.mielczarek on 15 Dec 2010 at 2:03

[GoogleCodeExporter]

Issue 423 has been merged into this issue.

Original comment by jessicag...@gmail.com on 31 May 2011 at 8:47

[GoogleCodeExporter]

Issue 429 has been merged into this issue.

Original comment by jessicag...@gmail.com on 16 Jun 2011 at 12:07

[GoogleCodeExporter]

This test was removed.

Original comment by ted.mielczarek on 18 Jul 2012 at 1:21

• Changed state: Fixed