This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Force array coercion in c_get_string

From: Pedro Alves <palves at redhat dot com>
To: Tom Tromey <tromey at adacore dot com>
Cc: gdb-patches at sourceware dot org
Date: Fri, 26 Apr 2019 17:42:15 +0100
Subject: Re: [PATCH] Force array coercion in c_get_string
References: <20190425181740.18062-1-tromey@adacore.com> <6d0c9915-cb2d-b7c2-1336-9347c90d22e6@redhat.com> <87v9z19auk.fsf@tromey.com> <877ebh7sve.fsf@tromey.com>

On 4/25/19 9:05 PM, Tom Tromey wrote:

>The actual patch is somewhat more
>     complicated than you might think, because the caller can request more
>     array elements than the type allows.  This is normal when the type is
>     using the C struct hack.

Which test exposes this issue?

I'm a bit confused here.  If we ever coerce an array and then read more
elements than the type allows, won't we be reading garbage passed the
coerced array elements?

Thanks,
Pedro Alves

Follow-Ups:
- Re: [PATCH] Force array coercion in c_get_string
  - From: Tom Tromey

References:
- [PATCH] Force array coercion in c_get_string
  - From: Tom Tromey
- Re: [PATCH] Force array coercion in c_get_string
  - From: Pedro Alves
- Re: [PATCH] Force array coercion in c_get_string
  - From: Tom Tromey
- Re: [PATCH] Force array coercion in c_get_string
  - From: Tom Tromey

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]