This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: one-too-many location in breakpoint
- From: Joel Brobecker <brobecker at adacore dot com>
- To: "Maciej W. Rozycki" <macro at codesourcery dot com>
- Cc: Tom Tromey <tromey at redhat dot com>, gdb-patches at sourceware dot org
- Date: Fri, 9 Dec 2011 09:19:19 +0100
- Subject: Re: one-too-many location in breakpoint
- References: <20111123163917.GA13809@adacore.com> <m38vn6y8v6.fsf@fleche.redhat.com> <20111123232406.GQ13809@adacore.com> <20111124105603.GA91879@adacore.com> <20111124163304.GR13809@adacore.com> <m31ussq6o2.fsf@fleche.redhat.com> <20111129033329.GS24943@adacore.com> <m38vmyoqg5.fsf@fleche.redhat.com> <m3obvun9vl.fsf@fleche.redhat.com> <alpine.DEB.1.10.1112081556410.5354@tp.orcam.me.uk>
> I can see you made this adjustment:
>
> - gdb_test "break ${class}::foo if (a == 3)" "Breakpoint (\[0-9\]).*"
> + gdb_test "break ${class}::hibob if (a_param == 3)" "Breakpoint
>
> but there's this definition elsewhere in this test case:
>
> set conditional1 "if (a == 3)"
>
> as well, that you have left intact. Should it be adjusted accordingly?
I think it did get adjusted yesterday.
> Why is this condition accepted for some targets and not for some
> others anyway?
Tom said:
> I missed a spot when changing the parameter names in ovsrch.exp, and
> didn't notice because I have the 64-bit glibc debuginfo installed, which
> provides a minsym named "a".
I've hit this sort of problem several times in the past, and that's why
I choose funky and unambiguous names for my global variables....
--
Joel