Turns out this fix doesn't work for main(). I've opened a new ticket for
that situation, but may not get around to digging into it for a while.
Often turning on optimization along with debugging will result in the
correct offsets being provided to gdb. Plain old "-O" will probably do it.
Peter
On Fri, Oct 7, 2011 at 1:14 PM, Peter Bigot
<pabi...@users.sourceforge.net>wrote:
> A patch for SF 3417263 has been added to the LTS-20110716 patch set at
> http://sourceforge.net/projects/mspgcc/files/Patches/LTS/20110716/.
> This fixes a problem with gdb being able to find local variables in
> unoptimized code (or, possibly, other situations where the frame
> pointer is present).
>
> It should have no effect if you don't use gdb. I don't promise it
> fixes all gdb problems. It does seem to fix the one in this bug
> report. If you can reproduce others, please file a tracker ticket at
> http://sourceforge.net/tracker/?group_id=42303&atid=432701.
>
> Peter
>
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
