This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [OBV PATCH 1/4] Add a newline in output messages
- From: Yao Qi <yao at codesourcery dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: <gdb-patches at sourceware dot org>
- Date: Thu, 6 Mar 2014 14:43:12 +0800
- Subject: Re: [OBV PATCH 1/4] Add a newline in output messages
- Authentication-results: sourceware.org; auth=none
- References: <1394023608-10761-1-git-send-email-yao at codesourcery dot com> <1394023608-10761-2-git-send-email-yao at codesourcery dot com> <20140305142236 dot GA16858 at adacore dot com>
On 03/05/2014 10:22 PM, Joel Brobecker wrote:
> Obvious indeed.
>
Patch is pushed in.
> The error handling is a little different from the usual, where error
> would typically be used; especially since zero can be a valid number.
Yes, a message is printed out, and let the caller to decide whether to
throw an error.
> And this leads to this sort of odd behavior:
>
> (gdb) set $v := 1.1
> (gdb) b a
> Breakpoint 1 at 0x401558: file a.adb, line 3.
> (gdb) cond $v 1 = 1
> Convenience variable must have integer value.
> Bad breakpoint argument: '$v 1 = 1'
Sorry, I don't find anything odd here. Is the odd behavior to print two
lines for an invalid input?
--
Yao (éå)