From eb6e10cb73e319a8d4651df7df667cd14b26ec70 Mon Sep 17 00:00:00 2001 From: Kazu Hirata Date: Tue, 21 Nov 2000 02:24:32 +0000 Subject: 2000-11-20 Kazu Hirata * bfd-in.h: Fix formatting. * bfd-in2.h: Likewise. * bfd.c: Likewise. * bout.c: Likewise. --- bfd/bfd.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'bfd/bfd.c') diff --git a/bfd/bfd.c b/bfd/bfd.c index e11aaf4..3372708 100644 --- a/bfd/bfd.c +++ b/bfd/bfd.c @@ -833,7 +833,7 @@ DESCRIPTION Instead, we want to ask questions like "is this NNN byte sized object I'm about to try read from file offset YYY reasonable?" As as example of where we might do this, some object formats - use string tables for which the first <> bytes of the + use string tables for which the first <> bytes of the table contain the size of the table itself, including the size bytes. If an application tries to read what it thinks is one of these string tables, without some way to validate the size, and for @@ -980,7 +980,7 @@ bfd_scan_vma (string, end, base) int digit; /* Let the host do it if possible. */ - if (sizeof(bfd_vma) <= sizeof(unsigned long)) + if (sizeof (bfd_vma) <= sizeof (unsigned long)) return (bfd_vma) strtoul (string, (char **) end, base); /* A negative base makes no sense, and we only need to go as high as hex. */ -- cgit v1.1