This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RE: [PATCH v2 3/3] btrace, frame: fix crash in get_frame_type
- From: "Metzger, Markus T" <markus dot t dot metzger at intel dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Thu, 11 Feb 2016 16:06:14 +0000
- Subject: RE: [PATCH v2 3/3] btrace, frame: fix crash in get_frame_type
- Authentication-results: sourceware.org; auth=none
- References: <1454681922-2228-1-git-send-email-markus dot t dot metzger at intel dot com> <1454681922-2228-3-git-send-email-markus dot t dot metzger at intel dot com> <56B9D620 dot 2020104 at redhat dot com> <A78C989F6D9628469189715575E55B233325FC44 at IRSMSX104 dot ger dot corp dot intel dot com> <56BA61C6 dot 8060807 at redhat dot com> <A78C989F6D9628469189715575E55B233325FF30 at IRSMSX104 dot ger dot corp dot intel dot com> <56BB0A0D dot 80502 at redhat dot com> <A78C989F6D9628469189715575E55B233325FFC6 at IRSMSX104 dot ger dot corp dot intel dot com> <A78C989F6D9628469189715575E55B233326016F at IRSMSX104 dot ger dot corp dot intel dot com> <56BB5872 dot 2000604 at redhat dot com> <A78C989F6D9628469189715575E55B2333260590 at IRSMSX104 dot ger dot corp dot intel dot com> <56BC8EF0 dot 4000202 at redhat dot com> <A78C989F6D9628469189715575E55B2333260743 at IRSMSX104 dot ger dot corp dot intel dot com> <56BCAF8D dot 8030303 at redhat dot com>
> -----Original Message-----
> From: Pedro Alves [mailto:palves@redhat.com]
> Sent: Thursday, February 11, 2016 4:58 PM
> To: Metzger, Markus T <markus.t.metzger@intel.com>
> Cc: gdb-patches@sourceware.org
> Subject: Re: [PATCH v2 3/3] btrace, frame: fix crash in get_frame_type
> >> If we don't know where the caller is, we can't skip the resolver in
> >> one go, so best to do is probably to return 0, and let infrun's
> >> stepping logic continue single-stepping.
> >
> > You think we should add the check nevertheless in gdb/glibc-tdep.c?
>
> Let's leave it be. If may be that the use case that trips on it would be best
> fixed differently.
>
> >
> > The others I won't be able to test. I could do the changes and rely
> > on buildbot to flag issues. If we really want to change them.
>
> I don't think we should change the others without evidence that they'd need
> it.
> If we do trip on problems on those, I think the fix should be elsewhere.
>
> I'd still early in the release cycle, let's wait and see.
OK. I'll send the complete series again.
Pathes 1 and 2 are unchanged and you've seen almost everything of patch 3,
already. Actually, patch 2 has been replaced by a completely unrelated patch,
but you've OK'ed it already in your last reply.
Thanks a lot for your review and for pointing out issues!
Regards,
Markus.
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
- References:
- [PATCH v2 1/3] frame: add skip_tailcall_frames
- [PATCH v2 3/3] btrace, frame: fix crash in get_frame_type
- Re: [PATCH v2 3/3] btrace, frame: fix crash in get_frame_type
- RE: [PATCH v2 3/3] btrace, frame: fix crash in get_frame_type
- Re: [PATCH v2 3/3] btrace, frame: fix crash in get_frame_type
- RE: [PATCH v2 3/3] btrace, frame: fix crash in get_frame_type
- Re: [PATCH v2 3/3] btrace, frame: fix crash in get_frame_type
- RE: [PATCH v2 3/3] btrace, frame: fix crash in get_frame_type
- RE: [PATCH v2 3/3] btrace, frame: fix crash in get_frame_type
- Re: [PATCH v2 3/3] btrace, frame: fix crash in get_frame_type
- RE: [PATCH v2 3/3] btrace, frame: fix crash in get_frame_type
- Re: [PATCH v2 3/3] btrace, frame: fix crash in get_frame_type
- RE: [PATCH v2 3/3] btrace, frame: fix crash in get_frame_type
- Re: [PATCH v2 3/3] btrace, frame: fix crash in get_frame_type