From e17c3f3ee73287aedb98a6f0ca8fd4a9ddc2b9bd Mon Sep 17 00:00:00 2001 From: Rafael Espindola Date: Wed, 17 Feb 2016 16:48:00 +0000 Subject: Represent the dynamic table itself with a DynRegionInfo. The dynamic table is also an array of a fixed structure, so it can be represented with a DynReginoInfo. No major functionality change. The extra error checking is covered by existing tests with a broken dynamic program header. Idea extracted from r260488. I did the extra cleanups. llvm-svn: 261107 --- llvm/test/Object/corrupt.test | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'llvm/test') diff --git a/llvm/test/Object/corrupt.test b/llvm/test/Object/corrupt.test index 7208566c25b..3ce7dc7f5e9 100644 --- a/llvm/test/Object/corrupt.test +++ b/llvm/test/Object/corrupt.test @@ -55,7 +55,7 @@ RUN: not llvm-readobj -dyn-relocations \ RUN: %p/Inputs/corrupt-invalid-dynamic-table-size.elf.x86-64 2>&1 | \ RUN: FileCheck --check-prefix=DYN-TABLE-SIZE %s -DYN-TABLE-SIZE: Invalid dynamic table size +DYN-TABLE-SIZE: Invalid entity size RUN: not llvm-readobj -dyn-relocations \ -- cgit v1.2.3