http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49951
--- Comment #19 from asmwarrior <asmwarrior at gmail dot com> ---
Hi, I see this bug happens at least in GCC 4.8.2 again. I'm using MinGW-Build
GCC 4.8.2 under Windows, and debug Codeblocks. I have a source code which have
something like:
void CompilerGCC::SetupEnvironment()
{
....
wxString currentPath;
....
}
But When I debug through lines using the step command, I see that the caret
still go back the the local variable definition of the line "wxString
currentPath".
I tried the simple test code that Peter Thompson gives, but it works fine, So
it looks like this bug happens in a larger project not the simple one.
Currently I don't have much way to show you. When I see the disassembler code,
I see some call to destructor of wxString.
0x64B0CF81 call 0x64b4f094 <InfoWindow::Display(wxString const&, wxString
const&, unsigned int, unsigned int)>
0x64B0CF86 lea eax,[ebp-0x34]
0x64B0CF89 mov ecx,eax
0x64B0CF8B call 0x64b5c090 <wxString::~wxString()>
0x64B0CF90 lea eax,[ebp-0x38]
0x64B0CF93 mov ecx,eax
0x64B0CF95 call 0x64b5c090 <wxString::~wxString()>
0x64B0CF9A lea eax,[ebp-0x30]
0x64B0CF9D mov DWORD PTR [esp],0x64b6bc70
0x64B0CFA4 mov ecx,eax
When I run
> info line *0x64B0CFDB
[debug]Line 801 of "F:\cb_sf_git\trunk\src\plugins\compilergcc\compilergcc.cpp"
starts at address 0x64b0cf9a <CompilerGCC::SetupEnvironment()+3258> and ends at
0x64b0cfe0 <CompilerGCC::SetupEnvironment()+3328>.
[debug]F:\cb_sf_git\trunk\src\plugins\compilergcc\compilergcc.cpp:801:32074:beg:0x64b0cf9a
But it looks like this is not enough information I can show you, any suggest
how to see the incorrect line-code map? Thanks.
