On Mon, 18 May 2009, Peter Denison wrote:
> On Mon, 18 May 2009, Peter Denison wrote:
>
>> Now, on to the actual crash. I will do more investigation, but for now,
>> here's the backtrace:
>>
>> Starting program: /src/.libs/lt-openocd -f
>> ../../../openocd-usr8200-jlink.cfg
>> Open On-Chip Debugge
On Mon, 18 May 2009, Peter Denison wrote:
> Now, on to the actual crash. I will do more investigation, but for now,
> here's the backtrace:
>
> Starting program: /src/.libs/lt-openocd -f
> ../../../openocd-usr8200-jlink.cfg
> Open On-Chip Debugger 0.2.0-in-development (2009-05-18-18:52) svn:1827
> > Try using
> >
> > libtool gdb ../openocd
> >
> > or the more pedantic (but future-proof):
> >
> > libtool --mode=execute gdb ../openocd
>
> Once a solution has been identified, it would be nice to have
> the BUGS file updated...
>
> --
for dev work it is often easier to config
On Mon, 18 May 2009, Øyvind Harboe wrote:
Try using
libtool gdb ../openocd
or the more pedantic (but future-proof):
libtool --mode=execute gdb ../openocd
Once a solution has been identified, it would be nice to have the BUGS
file updated...
Excellent! That (to be precise the
On Mon, 2009-05-18 at 21:51 +0200, Øyvind Harboe wrote:
> > Try using
> >
> >libtool gdb ../openocd
> >
> > or the more pedantic (but future-proof):
> >
> >libtool --mode=execute gdb ../openocd
>
> Once a solution has been identified, it would be nice to have the BUGS
> file update
> Try using
>
> libtool gdb ../openocd
>
> or the more pedantic (but future-proof):
>
> libtool --mode=execute gdb ../openocd
Once a solution has been identified, it would be nice to have the BUGS
file updated...
--
Øyvind Harboe
Embedded software and hardware consulting services
h
On Mon, 2009-05-18 at 19:33 +0100, Peter Denison wrote:
> On Mon, 18 May 2009, Øyvind Harboe wrote:
>
> [Oops - failed to copy the original to the list...]
> > On Mon, May 18, 2009 at 8:21 AM, Peter Denison
> > wrote:
> >> On Sat, 16 May 2009, Øyvind Harboe wrote:
> >>
> >>> Could you post a GDB
On Mon, 18 May 2009, Øyvind Harboe wrote:
$ gdb ../openocd --args openocd
... ends up running /usr/bin/openocd ...
Try
gdb --args openocd -f interface/xxx.cfg -f target/.cfg ...
This runs the one (r1409) in /usr/bin, not my newly compiled one.
If I find the actual executable, which I
> $ gdb ../openocd --args openocd
> ... ends up running /usr/bin/openocd ...
Try
gdb --args openocd -f interface/xxx.cfg -f target/.cfg ...
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
___
Open
On Mon, 18 May 2009, Øyvind Harboe wrote:
[Oops - failed to copy the original to the list...]
On Mon, May 18, 2009 at 8:21 AM, Peter Denison wrote:
On Sat, 16 May 2009, Øyvind Harboe wrote:
Could you post a GDB backtrace?
See:
http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
I trie
On Sat, 9 May 2009, Øyvind Harboe wrote:
Please report any problems you are experiencing with svn head.
Except for the performance regressions, which will be addressed
next week, there are no reported problems at this point w.r.t.
the JTAG API changes.
Every *other* time I run, I get this...
Please report any problems you are experiencing with svn head.
Except for the performance regressions, which will be addressed
next week, there are no reported problems at this point w.r.t.
the JTAG API changes.
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consultin
12 matches
Mail list logo
