W dniu 2012-05-11 16:06, Stian Skjelstad pisze:
> Freddie, I don't have a system available at the moment; Could you:
>
> shell> arm-none-eabi-gdb
> gdb> show arm abi<-- what does it state?
The current ARM ABI is "auto" (currently "APCS").
> gdb> file your-file-here.elf
> gdb> show arm abi<--
> Today I've found that when I use new GDB with new OpenOCD it does not
> work, but works perfectly fine when GDB is handled by Eclipse's GDB
> Hardware Debugging.
Freddie, I don't have a system available at the moment; Could you:
shell> arm-none-eabi-gdb
gdb> show arm abi <-- w
On Tue, May 08, 2012 at 06:36:36PM -0700, Luke wrote:
> To do this properly, it seems like openocd would have to be aware of
> which version of gdb was going to be used with it, and conditionally
> compile this file appropriately. Alternatively, a future release of
> OpenOCD could simply require g
>>> perhaps there is a way to determine the version of gdb at runtime,
>>> and act appropriately?
>> ..
>>> Thoughts?
>>
>> Please investigate the above, and if you will then please do it fast,
>> to get this resolved now.
>
>I looked at this a while back, and AFAICT version information of any k
On 09/05/12 12:16, Stian Skjelstad wrote:
perhaps there is a way to determine the version of gdb at runtime,
and act appropriately?
>>> ..
Thoughts?
>>>
>>> Please investigate the above, and if you will then please do it fast,
>>> to get this resolved now.
>>
>> I looked at this a
On Tue, May 8, 2012 at 10:42 PM, Luke wrote:
> I'm in the same boat as you -- is your quick fix still holding up and
> working well?
Yep, I've been using it ever since I wrote the first email to the list.
Perhaps it would be good enough to add an option to openocd that makes
it compatible with o
On 09/05/12 02:50, Peter Stuge wrote:
> Luke wrote:
>> perhaps there is a way to determine the version of gdb at runtime,
>> and act appropriately?
> ..
>> Thoughts?
>
> Please investigate the above, and if you will then please do it fast,
> to get this resolved now.
I looked at this a while back
Luke wrote:
> perhaps there is a way to determine the version of gdb at runtime,
> and act appropriately?
..
> Thoughts?
Please investigate the above, and if you will then please do it fast,
to get this resolved now.
//Peter
--
> What would be needed to make this fix acceptable so that OpenOCD would
> have no issues with newer versions of GDB?
I have applied this patch and now the latest openocd master (with this
patch applied) works with Linaro GCC 4.7-2012.4 and Linaro GDB
7.4-2012.4. I'm not sure at what point gdb sw
> I'd like to fix openocd the right way, but right now I'm more
> interested in getting my board up and running.
I'm in the same boat as you -- is your quick fix still holding up and
working well?
What would be needed to make this fix acceptable so that OpenOCD would
have no issues with newer ver
On Sun, Feb 12, 2012 at 8:26 PM, Peter Stuge wrote:
> Please do push a proper patch to Gerrit. Note that the patch you
> linked to is no such thing, it's just a quick hack which breaks
> compatibility.
Yep, I saw that, but it does fix openocd to work with newer gdb
versions, so that's what I'm us
Flemming Frandsen wrote:
> Hi, I've just been bitten in the ass by this issue (openocd returns
> the wrong number of registers to GDB):
> http://www.mail-archive.com/openocd-development@lists.berlios.de/msg14805.html
>
> I noticed the patch was posted in 2010, so I was a bit surprised that
> there
Hi, I've just been bitten in the ass by this issue (openocd returns
the wrong number of registers to GDB):
http://www.mail-archive.com/openocd-development@lists.berlios.de/msg14805.html
I noticed the patch was posted in 2010, so I was a bit surprised that
there isn't any sign of a solution in 0.5.
13 matches
Mail list logo
