This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH][PR breakpoints/16606] AVR8 breakpoint out of range, decrement pc after break
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Pierre Langlois <pierre dot langlois at embecosm dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 12 Mar 2014 09:07:59 +0100
- Subject: Re: [PATCH][PR breakpoints/16606] AVR8 breakpoint out of range, decrement pc after break
- Authentication-results: sourceware.org; auth=none
- References: <531A2316 dot 5090507 at embecosm dot com> <20140310110809 dot GC4882 at adacore dot com> <531EFA75 dot 10008 at embecosm dot com>
> I just realized that support for multiple address spaces was added
> but never documented.
> So the way to solve the issue is to add the @code qualifier as such:
>
> (gdb) break * (@code void *) 0x10e
>
> And it will set the TYPE_CODE_SPACE instance flag to the type when
> calling integer_to_address.
>
> However, shouldn't @code be the default for breakpoints?
I am not really sure about that. I know my example is not going to be
the most frequent situation ever, but what if the code is data memory?
I admit I didn't know about the @code, is there an equivalent for
data pointers as well? If that were a yes, I think we could argue
that indeed, @code would be a better default, and look into what
it would take to make that happen.
--
Joel