On Wed, Mar 7, 2012 at 3:43 PM, Tomek CEDRO wrote:
> Hey Drasko, I build defaul configuration and the debug symbols are just
> there I can debug at will no need to change or redefine anything, except
> something changed in this matter recently..? :-)
> Best regards,
> Tomek
Hmm... I do not know,
Hey Drasko, I build defaul configuration and the debug symbols are just
there I can debug at will no need to change or redefine anything, except
something changed in this matter recently..? :-)
Best regards,
Tomek
--
Virtua
> '-g -O2' should be the default configure CFLAGS.
> If i need to override for debugging i just do
>
> ./configure ... CFLAGS='-g -O0'
Yes, important not to use -O0 with a number higher than 0, else strang
things might happen when you want to singlestep and/or looking at local
variables.
Stian
On 7 March 2012 12:28, Drasko DRASKOVIC wrote:
> Hi all,
> I was wondering wat's the best way to compile OpenOCD binaty with
> debug information.
>
> I'd like to run OpenOCD in GDB and debug it itself, because I run into
> some problems with MIPS target initialization.
>
> Currently I am redefinin
On Wed, Mar 07, 2012 at 02:41:14PM +0100, Edgar Grimberg wrote:
> > Currently I am redefining CFLAGS in ./configure, something like
> > CFLAGS="$CFLAGS -g ...", but I am suspecting that there might be some
> > more elegant way to do this.
>
> How about:
> # export CFLAGS="-g"
> # ./configure
>
>
> Currently I am redefining CFLAGS in ./configure, something like
> CFLAGS="$CFLAGS -g ...", but I am suspecting that there might be some
> more elegant way to do this.
How about:
# export CFLAGS="-g"
# ./configure
or even in one line:
CFLAGS="-g" ; . ./configure
Edgar
Hi all,
I was wondering wat's the best way to compile OpenOCD binaty with
debug information.
I'd like to run OpenOCD in GDB and debug it itself, because I run into
some problems with MIPS target initialization.
Currently I am redefining CFLAGS in ./configure, something like
CFLAGS="$CFLAGS -g ...
