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 v2 02/10] Change dwarf2_frame_state_reg_info::reg to be std::vector

From: Tom Tromey <tom at tromey dot com>
To: Pedro Alves <palves at redhat dot com>
Cc: Tom Tromey <tom at tromey dot com>, gdb-patches at sourceware dot org
Date: Wed, 03 Oct 2018 15:04:53 -0600
Subject: Re: [PATCH v2 02/10] Change dwarf2_frame_state_reg_info::reg to be std::vector
References: <20181002044420.17628-1-tom@tromey.com> <20181002044420.17628-3-tom@tromey.com> <e9adc88f-3634-e598-6b61-2962d6b97348@redhat.com>

>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:

Pedro> On 10/02/2018 05:44 AM, Tom Tromey wrote:
>> This changes dwarf2_frame_state_reg_info::reg to be a std::vector.
>> This avoids undefined behavior in the copy constructor when the
>> original object does not have any registers.

Pedro> I don't have anything to say against the patch, I think it's a nice
Pedro> cleanup regardless, but could you expand this log a little to point
Pedro> out exactly what is triggering the undefined behavior.  I guess we're
Pedro> passing NULL to the memcpy?

Yes, that was the issue.  Simon asked for this cleanup IIRC.
I've added a note about this to the commit message.

Tom

References:
- [PATCH v2 00/10] Undefined Behavior Sanitizer, this time with docs
  - From: Tom Tromey
- [PATCH v2 02/10] Change dwarf2_frame_state_reg_info::reg to be std::vector
  - From: Tom Tromey
- Re: [PATCH v2 02/10] Change dwarf2_frame_state_reg_info::reg to be std::vector
  - From: Pedro Alves

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