News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

The 07 January 2012 build (7678) DEBUGGER BRANCH version is out.

Started by killerbot, January 07, 2012, 07:24:37 PM

Previous topic - Next topic

oBFusCATed

renega_666: Thanks for the report, I've added it to my todo and I'll see what is wrong with it later today (hopefully).
(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!]

Jenna

I found two minor issues:
if I add the same variable twice, it's also shown twice in the watches list.
The expected behaviour would be to select it in the watches window, or just do nothing.

And dragging a variable into the watches window without pressing control deletes it in the editor.
If I remember correctly this was fxed some time ago, but I'm not sure absolutely about that.
I can look into the second issue this evening.

oBFusCATed

Quote from: jens on January 26, 2012, 05:37:10 PM
I found two minor issues:
if I add the same variable twice, it's also shown twice in the watches list.
The expected behaviour would be to select it in the watches window, or just do nothing.
Are you sure this is needed? I'm not, because sometimes you may want to have to watches with different options.

Quote from: jens on January 26, 2012, 05:37:10 PM
And dragging a variable into the watches window without pressing control deletes it in the editor.
If I remember correctly this was fxed some time ago, but I'm not sure absolutely about that.
I can look into the second issue this evening.
No, it has never been fixed, last time I've reported this, you said it was working correctly for you.
I'll be happy if you're able to fix it.
(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!]

MortenMacFly

Quote from: oBFusCATed on January 26, 2012, 05:46:46 PM
Are you sure this is needed? I'm not, because sometimes you may want to have to watches with different options.
Indeed. For example, if you watch array (matrices) or vectors. Often you want to see only a certain elements / rows / columns. I do this regularly.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

oBFusCATed

Can someone running windows and non-python enabled gdb confirm the parser problems reported by renega_666?
I've tried to reproduce the problem with the latest version of the branch and it works as expected.
(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!]

Jenna

Quote from: oBFusCATed on January 26, 2012, 05:46:46 PM
Quote from: jens on January 26, 2012, 05:37:10 PM
I found two minor issues:
if I add the same variable twice, it's also shown twice in the watches list.
The expected behaviour would be to select it in the watches window, or just do nothing.
Are you sure this is needed? I'm not, because sometimes you may want to have to watches with different options.

Agreed !

Quote from: oBFusCATed on January 26, 2012, 05:46:46 PM
Quote from: jens on January 26, 2012, 05:37:10 PM
And dragging a variable into the watches window without pressing control deletes it in the editor.
If I remember correctly this was fxed some time ago, but I'm not sure absolutely about that.
I can look into the second issue this evening.
No, it has never been fixed, last time I've reported this, you said it was working correctly for you.
I'll be happy if you're able to fix it.

Fixed in svn r7718 .

oBFusCATed

(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!]

renega_666

Hi!

Some news about the issue I reported two days ago:

1. I now have tested and reproduced the bug on my house computers (win7 32bits and 64 bits). The parser error is still here.
2. I've also tried to remove my configuration files from app data and start with a clean default config but unfortunately the bug still appears. (tried on win7 32/64 and winXp 32)
3. Then, I've followed ollydbg instructions to enable gdb python and the parser error still occurs (I've used the ollydbg build and followed the setup instructions on the wiki page) (only tried on win7 32bits)

Is there anything else I could try?

Btw I 'm still not able to view the debugger's debug log (the check box is checked but the log window doesn't appear, it does in the previous nightly).


oBFusCATed

Quote from: renega_666 on January 28, 2012, 04:53:21 PM
Btw I 'm still not able to view the debugger's debug log (the check box is checked but the log window doesn't appear, it does in the previous nightly).
The debug log was removed, because many users had trouble finding it.
Now the debug log messages are printed in the normal log, but they have the prefix [debug].

I'll change the naming of the option, so it is less confusing.
(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!]

oBFusCATed

Can I ask someone on windows to test the renega_666 examples and confirm, that there is a bug?
(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!]

MortenMacFly

Quote from: oBFusCATed on January 28, 2012, 07:23:39 PM
Can I ask someone on windows to test the renega_666 examples and confirm, that there is a bug?
Windows XP here, debugger branch, even path with spaces - the bug does not occur.
Maybe it is a modified debugger script?
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

oBFusCATed

Morten: Can you disable the 'watch scripts' and try again? Also make sure you have no python-enabled-gdb.

renega_666: Can you post the full build log and can you try the previous nightly, to verify it is still working?
(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!]

renega_666

Tested with the sample code provided in my firts post.

Results with r7550

- the bug doesn't occur

- Screenshot:

http://imageshack.us/photo/my-images/692/screenshot7550.png/

- log:

QuotePATH=.;C:\MinGW32\bin;D:\Perl\site\bin;D:\Perl\bin;C:\Python27\;C:\Python27\Scripts;C:\Program Files\NVIDIA Corporation\PhysX\Common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;D:\Program Files\Autodesk\Backburner\;C:\Program Files\Common Files\Autodesk Shared\;C:\Program Files\doxygen\bin;C:\swig;C:\Program Files\TortoiseSVN\bin;D:\Program Files\doxygen\bin;D:\Program Files\CMake 2.8\bin;D:\QtSDK\Qt\4.8.0\bin;%APPDATA%\Python\Scripts;C:\MinGW32\bin
Command-line: C:\MinGW32\bin\gdb.exe -nx -fullname  -quiet -args D:/Projects/Codeblocks/TestBugGDBParser/bin/Debug/TestBugGDBParser.exe
Working dir : D:\Projects\Codeblocks\TestBugGDBParser
> set prompt >>>>>>cb_gdb:
Reading symbols from D:\Projects\Codeblocks\TestBugGDBParser\bin\Debug\TestBugGDBParser.exe...done.
(gdb) >>>>>>cb_gdb:
> show version
GNU gdb (GDB) 7.4.50.20120119-cvs
Copyright (C) 2012 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 "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 att
>>>>>>cb_gdb:
> catch throw
Catchpoint 1 (throw)
>>>>>>cb_gdb:
> source D:\Codeblocks\share\codeblocks/scripts/stl-views-1.0.3.gdb
>>>>>>cb_gdb:
> source C:\MinGW32\bin\stl.gdb
source C:\MinGW32\bin\wx.gdb
>>>>>>cb_gdb:>>>>>>cb_gdb:
> directory D:/Projects/Codeblocks/TestBugGDBParser/
>>>>>>cb_gdb:
> break "D:/Projects/Codeblocks/TestBugGDBParser/main.cpp:21"
Breakpoint 2 at 0x401452: file D:\Projects\Codeblocks\TestBugGDBParser\main.cpp, line 21.
>>>>>>cb_gdb:
> run
gdb: windows_init_thread_list
[New Thread 6948.0xaec]
Breakpoint 2, main () at D:\Projects\Codeblocks\TestBugGDBParser\main.cpp:21
D:\Projects\Codeblocks\TestBugGDBParser\main.cpp:21:388:beg:0x401452
>>>>>>cb_gdb:
> set debugevents off
>>>>>>cb_gdb:
> bt 30
#0  main () at D:\Projects\Codeblocks\TestBugGDBParser\main.cpp:21
>>>>>>cb_gdb:
> whatis foo
type = Foo
>>>>>>cb_gdb:
> output foo
{
 mName = {
   static npos = <optimized out>,
   _M_dataplus = {
     <std::allocator<char>> = {
       <__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>},
     members of std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_Alloc_hider:
     _M_p = 0x252b84 "MyFoo"
   }
 },
 mBar = 0
}>>>>>>cb_gdb:
> whatis str
type = String
>>>>>>cb_gdb:
> output str
{
 static npos = <optimized out>,
 _M_dataplus = {
   <std::allocator<char>> = {
     <__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>},
   members of std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_Alloc_hider:
   _M_p = 0x252bb4 "My string"
 }
}>>>>>>cb_gdb:

Results with r7678

- the bug does occur.

- Screenshot:

http://imageshack.us/photo/my-images/407/screenshot7678.png/

- log:

QuoteBuilding to ensure sources are up-to-date
Selecting target:
Debug-Win32
Adding source dir: D:\Projects\Codeblocks\TestBugGDBParser\
Adding source dir: D:\Projects\Codeblocks\TestBugGDBParser\
Adding file: D:\Projects\Codeblocks\TestBugGDBParser\bin\Debug\TestBugGDBParser.exe
Changing directory to: D:/Projects/Codeblocks/TestBugGDBParser/.

[debug]PATH=.;C:\MinGW32\bin;D:\Perl\site\bin;D:\Perl\bin;C:\Python27\;C:\Python27\Scripts;C:\Program Files\NVIDIA Corporation\PhysX\Common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;D:\Program Files\Autodesk\Backburner\;C:\Program Files\Common Files\Autodesk Shared\;C:\Program Files\doxygen\bin;C:\swig;C:\Program Files\TortoiseSVN\bin;D:\Program Files\doxygen\bin;D:\Program Files\CMake 2.8\bin;D:\QtSDK\Qt\4.8.0\bin;%APPDATA%\Python\Scripts;C:\MinGW32\bin
[debug]Command-line: C:\MinGW32\bin\gdb.exe -nx -fullname  -quiet -args D:/Projects/Codeblocks/TestBugGDBParser/bin/Debug/TestBugGDBParser.exe
[debug]Working dir : D:\Projects\Codeblocks\TestBugGDBParser

Starting debugger: C:\MinGW32\bin\gdb.exe -nx -fullname  -quiet -args D:/Projects/Codeblocks/TestBugGDBParser/bin/Debug/TestBugGDBParser.exe
done

[debug]> set prompt >>>>>>cb_gdb:

Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints

[debug]Reading symbols from D:\Projects\Codeblocks\TestBugGDBParser\bin\Debug\TestBugGDBParser.exe...
[debug]done.
[debug](gdb)
[debug]>>>>>>cb_gdb:
[debug]> show version
[debug]GNU gdb (GDB) 7.4.50.20120119-cvs
[debug]Copyright (C) 2012 Free Software Foundation, Inc.
[debug]License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
[debug]This is free software: you are free to change and redistribute it.
[debug]There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
[debug]and "show warranty" for details.
[debug]This GDB was configured as "mingw32".
[debug]For bug reporting instructions, please see:
[debug]<http://www.gnu.org/software/gdb/bugs/>.
[debug]>>>>>>cb_gdb:
[debug]> set confirm off

Debugger name and version: GNU gdb (GDB) 7.4.50.20120119-cvs

[debug]>>>>>>cb_gdb:
[debug]> set width 0
[debug]>>>>>>cb_gdb:
[debug]> set height 0
[debug]>>>>>>cb_gdb:
[debug]> set breakpoint pending on
[debug]>>>>>>cb_gdb:
[debug]> set print asm-demangle on
[debug]>>>>>>cb_gdb:
[debug]> set unwindonsignal on
[debug]>>>>>>cb_gdb:
[debug]> set print elements 0
[debug]>>>>>>cb_gdb:
[debug]> set debugevents on
[debug]>>>>>>cb_gdb:
[debug]> set new-console on
[debug]>>>>>>cb_gdb:
[debug]> set disassembly-flavor att
[debug]>>>>>>cb_gdb:
[debug]> catch throw
[debug]Catchpoint 1 (throw)
[debug]>>>>>>cb_gdb:
[debug]> source D:\Codeblocks_New\share\codeblocks/scripts/stl-views-1.0.3.gdb
[debug]>>>>>>cb_gdb:
[debug]> source C:\MinGW32\bin\stl.gdb
source C:\MinGW32\bin\wx.gdb
[debug]>>>>>>cb_gdb:>>>>>>cb_gdb:
[debug]> directory D:/Projects/Codeblocks/TestBugGDBParser/
[debug]>>>>>>cb_gdb:
[debug]> break "D:/Projects/Codeblocks/TestBugGDBParser/main.cpp:21"
[debug]Breakpoint 2 at 0x401452: file D:\Projects\Codeblocks\TestBugGDBParser\main.cpp, line 21.
[debug]>>>>>>cb_gdb:
[debug]> run
[debug]gdb: windows_init_thread_list

Child process PID: 9116

[debug][New Thread 9116.0x14cc]
[debug]Breakpoint 2, main () at D:\Projects\Codeblocks\TestBugGDBParser\main.cpp:21
[debug]D:\Projects\Codeblocks\TestBugGDBParser\main.cpp:21:388:beg:0x401452
[debug]>>>>>>cb_gdb:

At D:\Projects\Codeblocks\TestBugGDBParser\main.cpp:21

[debug]> set debugevents off
[debug]>>>>>>cb_gdb:
[debug]> whatis str
[debug]type = String
[debug]>>>>>>cb_gdb:
[debug]> output str
[debug]{
[debug]  static npos = <optimized out>,
[debug]  _M_dataplus = {
[debug]    <std::allocator<char>> = {
[debug]      <__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>},
[debug]    members of std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_Alloc_hider:
[debug]    _M_p = 0x642bb4 "My string"
[debug]  }
[debug]}>>>>>>cb_gdb:
[debug]> whatis foo
[debug]type = Foo
[debug]>>>>>>cb_gdb:
[debug]> output foo
[debug]{
[debug]  mName = {
[debug]    static npos = <optimized out>,
[debug]    _M_dataplus = {
[debug]      <std::allocator<char>> = {
[debug]        <__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>},
[debug]      members of std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_Alloc_hider:
[debug]      _M_p = 0x642b84 "MyFoo"
[debug]    }
[debug]  },
[debug]  mBar = 0
[debug]}>>>>>>cb_gdb:

oBFusCATed

I've diffed the logs and there is not big differences in them.

The only suspicious thing in them is this:

>>>>>>cb_gdb:
> source D:\Codeblocks\share\codeblocks/scripts/stl-views-1.0.3.gdb
>>>>>>cb_gdb:
> source C:\MinGW32\bin\stl.gdb
source C:\MinGW32\bin\wx.gdb
>>>>>>cb_gdb:>>>>>>cb_gdb:



>>>>>>cb_gdb:
> source D:\Codeblocks_New\share\codeblocks/scripts/stl-views-1.0.3.gdb
>>>>>>cb_gdb:
> source C:\MinGW32\bin\stl.gdb
>>>>>>cb_gdb:>>>>>>cb_gdb:


I guess you've put this source commands in the initial commands.
Can you remove them and try again? Why are they different in the two versions?
(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!]

renega_666

Do you speak about stl-views-1.0.3.gdb ? or  C:\MinGW32\bin\stl.gdb?

I think I didn't do anything about the first source command, the second one is the one I added when following the ollydbg instructions to enable python gdb.

Here is a screenshot of my debugger settings: http://imageshack.us/photo/my-images/407/capturejnl.png/

Please tell me the name of the files/commands you want I to remove, I'm a little lost here...