Author Topic: The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.  (Read 20910 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5241
Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

Before you use a nightly make sure you understand how it works.

A link to the unicode windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw28u_gcc_cb_wx2810_gcc441.7z

For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://prdownload.berlios.de/codeblocks/mingwm10_gcc441.7z

The 09 October 2010 build is out.
  - Windows :
   http://prdownload.berlios.de/codeblocks/CB_20101009_rev6688_DEBUGGER_BRANCH_win32.7z
  - Linux :
   none

Important changes compared to previous DEBUGGER BRANCH nightly:

* debugger_branch: applied patch 16.10 with the following features:
- added tooltips to the watches window
- enabled the tooltips in the wxPG, please fix the windows project to enable them, too [Windows MISSING]
* all updates that occurred on trunk


Note: Watch parsing prints an error message in the watches window if the parsing fails. If you see this string please report it as a bug.

THIS IS A SPECIAL TEST BUILD OF REFACTORINGS CARRIED OUT ON THE DEBUGGER BRANCH IN OUR SVN.
FOCUS IS ON ENHANCED DEBUGGING USABILITY.

Give your feedback on this version only in this thread, don't mix it with the regular nightly please.

Once we don't have any blockers on this version,we will merge the changes into trunk and it will be part of the regular nightlies.

Offline jens

  • Administrator
  • Lives here!
  • *****
  • Posts: 7253
    • Jens' unofficial debian-repository for the Code::Blocks - IDE
Re: The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.
« Reply #1 on: October 09, 2010, 09:39:29 pm »
Debian packages (binaries and sources) for 32-bit and 64-bit systems can be found in my repo.

If you want to use apt (or dselect, synaptic or whatever) you need to add the following entries to /etc/apt/sources.list :
Code: [Select]
deb http://apt.jenslody.de/ any dbg
deb-src http://apt.jenslody.de/ any dbg
and remove entries for the normal nightlies.

Alternatively you can download the deb's directly from http://apt.jenslody.de/pool/dbg/c/codeblocks/ .

Revision is 6657, all later commits are commits to trunk or code-completion refactoring branch.

Offline Loaden

  • Lives here!
  • ****
  • Posts: 1014
Re: The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.
« Reply #2 on: October 13, 2010, 10:35:30 am »
about "added tooltips to the watches window", The look is always the value of the information displayed?
Can be displayed info of the columns?

Offline Loaden

  • Lives here!
  • ****
  • Posts: 1014
Re: The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.
« Reply #3 on: October 13, 2010, 10:37:49 am »
issue 2: Can not drag the variable if it is only one char.

Offline Loaden

  • Lives here!
  • ****
  • Posts: 1014
Re: The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.
« Reply #4 on: October 13, 2010, 10:53:08 am »
If there exist some watchs, will lead restart debug failed.
see the video demo:http://portablecb.googlecode.com/files/aaa.swf

[attachment deleted by admin]
« Last Edit: October 13, 2010, 10:55:29 am by Loaden »

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12688
    • Travis build status
Re: The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.
« Reply #5 on: October 13, 2010, 12:40:30 pm »
about "added tooltips to the watches window", The look is always the value of the information displayed?
Can be displayed info of the columns?
I think the tooltips weren't enabled on windows. Morten, I'm right?

If there exist some watchs, will lead restart debug failed.
see the video demo:http://portablecb.googlecode.com/files/aaa.swf
:) ... this is known problem...
Probably I should disable editing the value of watches which use script evaluators (wxString for example).
From the video it looks like you're using python enabled gdb?
Does the command for setting the value of std::string works?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Loaden

  • Lives here!
  • ****
  • Posts: 1014
Re: The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.
« Reply #6 on: October 13, 2010, 12:43:32 pm »
about "added tooltips to the watches window", The look is always the value of the information displayed?
Can be displayed info of the columns?
I think the tooltips weren't enabled on windows. Morten, I'm right?

If there exist some watchs, will lead restart debug failed.
see the video demo:http://portablecb.googlecode.com/files/aaa.swf
:) ... this is known problem...
Probably I should disable editing the value of watches which use script evaluators (wxString for example).
From the video it looks like you're using python enabled gdb?
Does the command for setting the value of std::string works?

Yes, I am use python support.
I can't change std::string value too.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12688
    • Travis build status
Re: The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.
« Reply #7 on: October 13, 2010, 01:58:28 pm »
I was asking if you can change the std::string value with raw gdb commands, not from the GUI.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Loaden

  • Lives here!
  • ****
  • Posts: 1014
Re: The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.
« Reply #8 on: October 13, 2010, 02:29:28 pm »
I was asking if you can change the std::string value with raw gdb commands, not from the GUI.
Quote
> p wxStr
$1 = "wxString Value Ref"
> p wxStr=L"Unicode String can be changed!"
$2 = "Unicode String can be changed!"
> p wxStr
$3 = "Unicode String can be changed!"
> p stdStr
$4 = "std::string value Ref"
> p stdStr=L"test"
$5 = ""
> p stdStr="test 2"
$6 = ""

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5234
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.
« Reply #9 on: October 13, 2010, 02:33:40 pm »
I was asking if you can change the std::string value with raw gdb commands, not from the GUI.
Quote
> p wxStr
$1 = "wxString Value Ref"
> p wxStr=L"Unicode String can be changed!"
$2 = "Unicode String can be changed!"
> p wxStr
$3 = "Unicode String can be changed!"
> p stdStr
$4 = "std::string value Ref"
> p stdStr=L"test"
$5 = ""
> p stdStr="test 2"
$6 = ""

Good.
it seems we can change the string value from the command line.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12688
    • Travis build status
Re: The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.
« Reply #10 on: October 13, 2010, 05:26:13 pm »
Loaden:
1. why are you use the "p" (print) command to change the value?
2. do you have the python scripts for wxWidgets?
3. can you give me the debug log (debugger's debug log) from the C::B?
4. does it work in trunk/cc?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Loaden

  • Lives here!
  • ****
  • Posts: 1014
Re: The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.
« Reply #11 on: October 14, 2010, 02:26:20 am »
Loaden:
1. why are you use the "p" (print) command to change the value?
2. do you have the python scripts for wxWidgets?
3. can you give me the debug log (debugger's debug log) from the C::B?
4. does it work in trunk/cc?
1. I'm just used to do this, it works well.
2. Yes, see: http://qp-gcc.googlecode.com/files/gdb-7.2.50.20101012.7z
4. Can work in the trunk (same with gdb commands)
3. see:
Code: [Select]
PATH=.;D:\DengYC\DEBUGBRANCH\sdk\wx\lib\gcc_dll;D:\DengYC\DEBUGBRANCH\build\gcc\bin;D:\DengYC\DEBUGBRANCH\tool;D:\DengYC\DEBUGBRANCH\tool\svn;D:\DengYC\DEBUGBRANCH\tool\vctool;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Common Files\Thunder Network\KanKan\Codecs;C:\Program Files\TortoiseSVN\bin
Command-line: D:\DengYC\DEBUGBRANCH\build\gcc\bin\gdb.exe -nx -fullname  -quiet -args bin/cmd.exe
Working dir : D:\DengYC\gdbpython-demo\
> set prompt >>>>>>cb_gdb:
Reading symbols from D:\DengYC\gdbpython-demo/bin/cmd.exe...done.
(gdb) >>>>>>cb_gdb:
> show version
GNU gdb (GDB) 7.2.50.20101012
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-mingw32".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
>>>>>>cb_gdb:
> set confirm off
>>>>>>cb_gdb:
> set width 0
>>>>>>cb_gdb:
> set height 0
>>>>>>cb_gdb:
> set breakpoint pending on
>>>>>>cb_gdb:
> set print asm-demangle on
>>>>>>cb_gdb:
> set unwindonsignal on
>>>>>>cb_gdb:
> set print elements -1
>>>>>>cb_gdb:
> set debugevents on
>>>>>>cb_gdb:
> set new-console on
>>>>>>cb_gdb:
> set disassembly-flavor intel
>>>>>>cb_gdb:
> catch throw
Catchpoint 1 (throw)
>>>>>>cb_gdb:
> source D:\DengYC\DEBUGBRANCH\share\codeblocks/scripts/stl-views-1.0.3.gdb
>>>>>>cb_gdb:
> source D:\DengYC\DEBUGBRANCH\build\gcc\bin\stl.gdb
source D:\DengYC\DEBUGBRANCH\build\gcc\bin\wx.gdb
>>>>>>cb_gdb:
> directory D:/DengYC/gdbpython-demo/
>>>>>>cb_gdb:>>>>>>cb_gdb:
> tbreak "D:/DengYC/gdbpython-demo/main.cpp:15"
Temporary breakpoint 2 at 0x4013ee: file D:\DengYC\gdbpython-demo\main.cpp, line 15.
>>>>>>cb_gdb:
> run
gdb: windows_init_thread_list
[New Thread 3880.0xf1c]
Temporary breakpoint 2, main () at D:\DengYC\gdbpython-demo\main.cpp:15
D:\DengYC\gdbpython-demo\main.cpp:15:159:beg:0x4013ee
>>>>>>cb_gdb:
> set debugevents off
>>>>>>cb_gdb:
> bt 30
#0  main () at D:\DengYC\gdbpython-demo\main.cpp:15
>>>>>>cb_gdb:
> next
D:\DengYC\gdbpython-demo\main.cpp:16:193:beg:0x401405
>>>>>>cb_gdb:
> bt 30
#0  main () at D:\DengYC\gdbpython-demo\main.cpp:16
>>>>>>cb_gdb:
> next
D:\DengYC\gdbpython-demo\main.cpp:17:218:beg:0x40141c
>>>>>>cb_gdb:
> bt 30
#0  main () at D:\DengYC\gdbpython-demo\main.cpp:17
>>>>>>cb_gdb:
> whatis &wxStr
type = wxString *
>>>>>>cb_gdb:
> output /c wxStr.m_pchData[0]@((wxStringData*)wxStr.m_pchData - 1)->nDataLength
{119 'w', 120 'x', 83 'S', 116 't', 114 'r', 105 'i', 110 'n', 103 'g', 32 ' ', 86 'V', 97 'a', 108 'l', 117 'u', 101 'e'}>>>>>>cb_gdb:
> set variable wxStr=L"aaa"
>>>>>>cb_gdb:
> whatis &wxStr
type = wxString *
>>>>>>cb_gdb:
> output /c wxStr.m_pchData[0]@((wxStringData*)wxStr.m_pchData - 1)->nDataLength
Cannot access memory at address 0xb694a8
>>>>>>cb_gdb:
> p wxStr=L"aaa"
$1 = "aaa"
>>>>>>cb_gdb:
> next
D:\DengYC\gdbpython-demo\main.cpp:18:258:beg:0x40145c
>>>>>>cb_gdb:
> whatis &wxStr
type = wxString *
>>>>>>cb_gdb:
> output /c wxStr.m_pchData[0]@((wxStringData*)wxStr.m_pchData - 1)->nDataLength
Cannot access memory at address 0xb69560
>>>>>>cb_gdb:
> bt 30
#0  main () at D:\DengYC\gdbpython-demo\main.cpp:18
>>>>>>cb_gdb:
> next
D:\DengYC\gdbpython-demo\main.cpp:19:288:beg:0x401491
>>>>>>cb_gdb:
> whatis &wxStr
type = wxString *
>>>>>>cb_gdb:
> output /c wxStr.m_pchData[0]@((wxStringData*)wxStr.m_pchData - 1)->nDataLength
Cannot access memory at address 0xb69560
>>>>>>cb_gdb:
> bt 30
#0  main () at D:\DengYC\gdbpython-demo\main.cpp:19
>>>>>>cb_gdb:
> whatis &stdStr
type = std::string *
>>>>>>cb_gdb:
> output stdStr
"std::string value">>>>>>cb_gdb:
> p stdStr=L"bbb"
$2 = ""
>>>>>>cb_gdb:
> next
D:\DengYC\gdbpython-demo\main.cpp:20:323:beg:0x40149d
>>>>>>cb_gdb:
> whatis &wxStr
type = wxString *
>>>>>>cb_gdb:
> output /c wxStr.m_pchData[0]@((wxStringData*)wxStr.m_pchData - 1)->nDataLength
Cannot access memory at address 0xb69560
>>>>>>cb_gdb:
> whatis &stdStr
type = std::string *
>>>>>>cb_gdb:
> output stdStr
"">>>>>>cb_gdb:
> bt 30
#0  main () at D:\DengYC\gdbpython-demo\main.cpp:20
>>>>>>cb_gdb:
> next
D:\DengYC\gdbpython-demo\main.cpp:21:342:beg:0x4014cf
>>>>>>cb_gdb:
> whatis &wxStr
type = wxString *
>>>>>>cb_gdb:
> output /c wxStr.m_pchData[0]@((wxStringData*)wxStr.m_pchData - 1)->nDataLength
Cannot access memory at address 0xb69560
>>>>>>cb_gdb:
> whatis &stdStr
type = std::string *
>>>>>>cb_gdb:
> output stdStr
"">>>>>>cb_gdb:
> bt 30
#0  main () at D:\DengYC\gdbpython-demo\main.cpp:21
>>>>>>cb_gdb:
> next
D:\DengYC\gdbpython-demo\main.cpp:22:361:beg:0x401501
>>>>>>cb_gdb:
> whatis &wxStr
type = wxString *
>>>>>>cb_gdb:
> output /c wxStr.m_pchData[0]@((wxStringData*)wxStr.m_pchData - 1)->nDataLength
Cannot access memory at address 0xb69560
>>>>>>cb_gdb:
> whatis &stdStr
type = std::string *
>>>>>>cb_gdb:
> output stdStr
"">>>>>>cb_gdb:
> bt 30
#0  main () at D:\DengYC\gdbpython-demo\main.cpp:22
>>>>>>cb_gdb:
> next
D:\DengYC\gdbpython-demo\main.cpp:23:394:beg:0x40150f
>>>>>>cb_gdb:
> whatis &wxStr
type = wxString *
>>>>>>cb_gdb:
> output /c wxStr.m_pchData[0]@((wxStringData*)wxStr.m_pchData - 1)->nDataLength
Cannot access memory at address 0xb69560
>>>>>>cb_gdb:
> whatis &stdStr
type = std::string *
>>>>>>cb_gdb:
> output stdStr
"">>>>>>cb_gdb:
> bt 30
#0  main () at D:\DengYC\gdbpython-demo\main.cpp:23
>>>>>>cb_gdb:
> whatis wxStr
type = wxString
>>>>>>cb_gdb:
> output &wxStr
(wxString *) 0x22feb4>>>>>>cb_gdb:
> output /c wxStr.m_pchData[0]@((wxStringData*)wxStr.m_pchData - 1)->nDataLength
Cannot access memory at address 0xb69560
>>>>>>cb_gdb:
> whatis wxStrRef
Attempt to take contents of a non-pointer value.
>>>>>>cb_gdb:
> output wxStrRef
"aaa">>>>>>cb_gdb:
> output wxStrRef
"aaa">>>>>>cb_gdb:
> output wxStrRef
"aaa">>>>>>cb_gdb:
> p wxStrRef
$3 = "aaa"
>>>>>>cb_gdb:
> next
Program received signal SIGSEGV, Segmentation fault.
0x77c17098 in msvcrt!memcpy () from C:\WINDOWS\system32\msvcrt.dll
>>>>>>cb_gdb:
> whatis &wxStr
No symbol "wxStr" in current context.
>>>>>>cb_gdb:
> output wxStr
No symbol "wxStr" in current context.
>>>>>>cb_gdb:
> whatis &stdStr
No symbol "stdStr" in current context.
>>>>>>cb_gdb:
> output stdStr
No symbol "stdStr" in current context.
>>>>>>cb_gdb:
> bt 30
#0  0x77c17098 in msvcrt!memcpy () from C:\WINDOWS\system32\msvcrt.dll
#1  0x684cffb6 in wxmsw28u!_ZN12wxStringBase10ConcatSelfEjPKwj () from D:\DengYC\DEBUGBRANCH\sdk\wx\lib\gcc_dll\wxmsw28u.dll
#2  0x0040e768 in wxStringBase::ConcatSelf (this=0x22feb4, nLen=4, src=0x4170a2 L" Ref") at D:/DengYC/DEBUGBRANCH/sdk/wx/include/wx/string.h:287
#3  0x0040e793 in wxStringBase::append (this=0x22feb4, sz=0x4170a2 L" Ref") at D:/DengYC/DEBUGBRANCH/sdk/wx/include/wx/string.h:448
#4  0x0040e7fc in wxStringBase::operator+= (this=0x22feb4, psz=0x4170a2 L" Ref") at D:/DengYC/DEBUGBRANCH/sdk/wx/include/wx/string.h:647
#5  0x0040e8c0 in wxString::operator+= (this=0x22feb4, psz=0x4170a2 L" Ref") at D:/DengYC/DEBUGBRANCH/sdk/wx/include/wx/string.h:1411
#6  0x00401526 in main () at D:\DengYC\gdbpython-demo\main.cpp:23
>>>>>>cb_gdb:
> frame 2
#2  0x0040e768 in wxStringBase::ConcatSelf (this=0x22feb4, nLen=4, src=0x4170a2 L" Ref") at D:/DengYC/DEBUGBRANCH/sdk/wx/include/wx/string.h:287
D:/DengYC/DEBUGBRANCH/sdk/wx/include/wx/string.h:287:9436:beg:0x40e768
>>>>>>cb_gdb:
> whatis &wxStr
No symbol "wxStr" in current context.
>>>>>>cb_gdb:
> output wxStr
No symbol "wxStr" in current context.
>>>>>>cb_gdb:
> whatis &stdStr
No symbol "stdStr" in current context.
>>>>>>cb_gdb:
> output stdStr
No symbol "stdStr" in current context.
>>>>>>cb_gdb:
> bt 30
#0  0x77c17098 in msvcrt!memcpy () from C:\WINDOWS\system32\msvcrt.dll
#1  0x684cffb6 in wxmsw28u!_ZN12wxStringBase10ConcatSelfEjPKwj () from D:\DengYC\DEBUGBRANCH\sdk\wx\lib\gcc_dll\wxmsw28u.dll
#2  0x0040e768 in wxStringBase::ConcatSelf (this=0x22feb4, nLen=4, src=0x4170a2 L" Ref") at D:/DengYC/DEBUGBRANCH/sdk/wx/include/wx/string.h:287
#3  0x0040e793 in wxStringBase::append (this=0x22feb4, sz=0x4170a2 L" Ref") at D:/DengYC/DEBUGBRANCH/sdk/wx/include/wx/string.h:448
#4  0x0040e7fc in wxStringBase::operator+= (this=0x22feb4, psz=0x4170a2 L" Ref") at D:/DengYC/DEBUGBRANCH/sdk/wx/include/wx/string.h:647
#5  0x0040e8c0 in wxString::operator+= (this=0x22feb4, psz=0x4170a2 L" Ref") at D:/DengYC/DEBUGBRANCH/sdk/wx/include/wx/string.h:1411
#6  0x00401526 in main () at D:\DengYC\gdbpython-demo\main.cpp:23
>>>>>>cb_gdb:
> frame 2
#2  0x0040e768 in wxStringBase::ConcatSelf (this=0x22feb4, nLen=4, src=0x4170a2 L" Ref") at D:/DengYC/DEBUGBRANCH/sdk/wx/include/wx/string.h:287
D:/DengYC/DEBUGBRANCH/sdk/wx/include/wx/string.h:287:9436:beg:0x40e768
>>>>>>cb_gdb:
> whatis stdStrRef
No symbol "stdStrRef" in current context.
>>>>>>cb_gdb:
> output stdStrRef
No symbol "stdStrRef" in current context.
>>>>>>cb_gdb:
> output stdStrRef
No symbol "stdStrRef" in current context.
>>>>>>cb_gdb:
> output stdStrRef
No symbol "stdStrRef" in current context.
>>>>>>cb_gdb:

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12688
    • Travis build status
Re: The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.
« Reply #12 on: October 14, 2010, 08:25:25 am »
If you're using gdb python scripts for wxWidgets you should disable the gdb_types.script (it is useless).
Also it is strange that the set command doesn't work...

Quote
4. Can work in the trunk (same with gdb commands)
Cannot compute :( .... does it work in trunk if you use the GUI or it doesn't?


p.s. your versions (or Ollygdb ones) of GDB are pretty broken, they spit too much warnings and this confuses the parser
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Loaden

  • Lives here!
  • ****
  • Posts: 1014
Re: The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.
« Reply #13 on: October 14, 2010, 10:33:23 am »
Quote
4. Can work in the trunk (same with gdb commands)
Cannot compute :( .... does it work in trunk if you use the GUI or it doesn't?
If changed the wxString's variable's value, it works well use GUI or use commands in trunk(or CC).
But if changed the std::string variable's value, they are not work.

You can trying trunk/CC by yourself, maybe you can get more information.

Offline Zadirion

  • Multiple posting newcomer
  • *
  • Posts: 10
Re: The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.
« Reply #14 on: October 25, 2010, 01:54:28 pm »
Hi,

Using this r6688 branch, I'm getting the following error during a debug session when I'm trying to step inside a CryptoPP function (more like a constructor but i don't think that's relevant):
Code: [Select]
Cannot open file: D:/testproject/../../testproject/third-party/cryptopp//cryptlib.h

This pops up in a notification window to the lower right corner and also in the debugger log in red.
I am noting that the "../../" in the path will evaluate to a path above D:/ which doesn't really make any sense. I'm not sure where the relative paths come from so I can't remove them.

Not sure if this is an error on my part or there is an issue with CB. Any ideas?

Thanks

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12688
    • Travis build status
Re: The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.
« Reply #15 on: October 25, 2010, 02:02:18 pm »
I guess that the paths stored in the debug info are wrong.
Please verify they are correct (I don't know how, sorry).

How are you building the CryptoPP lib?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Zadirion

  • Multiple posting newcomer
  • *
  • Posts: 10
Re: The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.
« Reply #16 on: October 25, 2010, 02:36:22 pm »
How are you building the CryptoPP lib?
The CryptoPP source files are directly included in the project. I'm not building CryptoPP as a separate library.

Quote
I guess that the paths stored in the debug info are wrong.
Please verify they are correct (I don't know how, sorry).
Well, the bummer is I don't know how either. Like you, I suspect wrong paths might be the reason this is failing.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12688
    • Travis build status
Re: The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.
« Reply #17 on: October 25, 2010, 03:01:15 pm »
Can you try different GCC and GDB (try several combinations)?
Can you give as the build log or a simple test project + sources.

I've made a little observation using variaous reports in the forum:
1. gcc 4.5.x causes problems with debugging (gdb 7.2 might work, I don't know for sure).
2. gdb works better in linux, the windows version is less stable.

(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline mushakk

  • Multiple posting newcomer
  • *
  • Posts: 54
Re: The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.
« Reply #18 on: November 19, 2010, 09:23:55 am »
Hi!

First say I love this branch. Are there some news?

I know maybe this is not the correct forum but I want to launch a proposal: When we add a pointer to the watches window I think will be better display the pointer address (like now) and have a + symbol to inspect the contents of the variable like if we had typed '*pointer'. This is the behavior of Visual Studio debugger that I think is more productive for the developer.

Thanks for your work and sorry about the intrusion.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12688
    • Travis build status
Re: The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.
« Reply #19 on: November 19, 2010, 10:05:48 am »
Can't be done (easily/reliably) with the current implementation.
There is a gdb/mi plugin in the works that does it already,
unfortunately I don't have much time to work on it at the moment.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline mushakk

  • Multiple posting newcomer
  • *
  • Posts: 54
Re: The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.
« Reply #20 on: November 19, 2010, 10:57:38 am »
In any case, thank you very much for your work!