Fix Fission (broken by my previous patch)
authorDavid Blaikie <dblaikie@gmail.com>
Tue, 18 Jul 2017 15:06:17 +0000 (16:06 +0100)
committerPedro Alves <palves@redhat.com>
Tue, 18 Jul 2017 15:06:17 +0000 (16:06 +0100)
commitc5ed057625f886b14d9def3fa7488fd8bbbf7dd3
treec4c7acef83f69ef5262f4aa97af8c34fdac7203d
parente4e21d9ed14c74304bc060a9d892c0edfc4c8ab4
Fix Fission (broken by my previous patch)

Turns out somewhere along the refactoring of the multiple-CU support
for Fission I broke the patch before submitting it (& seems to have
broken Fission support generally).

Syncing back to the point at which the patch was committed, the
previous test results on my machine are:

 expected passes: 36137
 unexpected failures: 416

with the previous (broken) patch committed:

 expected passes: 36131
 unexpected failures: 429

With this one line patch applied on top of the broken commit:

 expected passes: 36144
 unexpected failures: 416

(& all other result counts remained the same in all 3 cases)

gdb/ChangeLog:
2017-07-18  David Blaikie  <dblaikie@gmail.com>

* dwarf2read.c (create_cus_hash_table): Re-add lost initialization
of dwo_cu's dwo_file.
gdb/ChangeLog
gdb/dwarf2read.c