Author Topic: The 11 February 2012 build (7790) DEBUGGER BRANCH version is out.  (Read 60863 times)

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12067
    • Travis build status
Re: The 11 February 2012 build (7790) DEBUGGER BRANCH version is out.
« Reply #45 on: February 25, 2012, 12:58:30 pm »
Aradayn:
I think, I've fixed it. It seems that if I set the size of the dialog, before I add the sub panels to the treebook it doesn't crash.
Please test this patch and report if the problems is really fixed. I'll do some testing under linux and I will commit it after that.

Code: [Select]
Index: src/src/debuggersettingsdlg.cpp
===================================================================
--- src/src/debuggersettingsdlg.cpp (revision 7854)
+++ src/src/debuggersettingsdlg.cpp (working copy)
@@ -74,9 +74,11 @@
 
  Connect(ID_TREEBOOK,wxEVT_COMMAND_TREEBOOK_PAGE_CHANGED,(wxObjectEventFunction)&DebuggerSettingsDlg::OnPageChanged);
  //*)
+ SetMinSize(wxSize(600, 600));
+ SetSize(wxSize(600, 600));
 
     m_commonPanel = new DebuggerSettingsCommonPanel(m_treebook);
- m_treebook->AddPage(m_commonPanel, _("Common"));
+ m_treebook->AddPage(m_commonPanel, _("Common"), true);
 
     DebuggerManager::RegisteredPlugins &plugins = Manager::Get()->GetDebuggerManager()->GetAllDebuggers();
     for (DebuggerManager::RegisteredPlugins::iterator it = plugins.begin(); it != plugins.end(); ++it)
@@ -101,9 +103,6 @@
 
     for (size_t ii = 0; ii < m_treebook->GetPageCount(); ++ii)
         m_treebook->ExpandNode(ii);
-
- SetMinSize(wxSize(600, 600));
- SetSize(wxSize(600, 600));
 }
 
 DebuggerSettingsDlg::~DebuggerSettingsDlg()
(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 Aradayn

  • Single posting newcomer
  • *
  • Posts: 8
Re: The 11 February 2012 build (7790) DEBUGGER BRANCH version is out.
« Reply #46 on: February 28, 2012, 05:06:55 pm »
Thanks, oBFusCATed! That seems to have done the trick. I see the full debugger name and it didn't crash.

Offline ricardo

  • Single posting newcomer
  • *
  • Posts: 2
    • CodeSourcery
Re: The 11 February 2012 build (7790) DEBUGGER BRANCH version is out.
« Reply #47 on: March 20, 2012, 12:10:17 am »
Code: [Select]
Index: src/sdk/pipedprocess.cpp
===================================================================
--- src/sdk/pipedprocess.cpp    (revision 7821)
+++ src/sdk/pipedprocess.cpp    (working copy)
@@ -148,6 +148,7 @@
     if (pOut)
     {
         wxTextOutputStream sin(*pOut);
+        sin.SetMode(wxEOL_UNIX);
         wxString msg = text + _T('\n');
         sin.WriteString(msg);
     }

Here is the patch that makes it work.
The reason is that this version of gdb treats both \n and \m as new command markers.
So using \n\m triggers as two commands:
1. the actual command
2. the re execution of the command, because most debuggers treat empty commands as "repeat-last-command", this is a feature to simplify usage.

I'm not CodeSourcery support, but I suspect that using DOS style line endings triggers the double execution problem exactly as oBFusCATed has laid out above.  Switching to Unix style line endings is the right fix.  Does anyone know if CodeSourcery's GDB is alone in this behavior or if the FSF's GDB also exhibits this behavior?

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12067
    • Travis build status
Re: The 11 February 2012 build (7790) DEBUGGER BRANCH version is out.
« Reply #48 on: March 20, 2012, 08:49:01 am »
There is not FSF build of GDB for windows. The mingw one works OK with the native line endings.
(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 ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5230
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: The 11 February 2012 build (7790) DEBUGGER BRANCH version is out.
« Reply #49 on: March 28, 2012, 09:57:07 am »
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/ .
Linux newbie. (I'm using Ubuntu 10.04 in a virtualbox under winXP)
I tried the method described here:http://apt.jenslody.de/

I have correctly set the file: /etc/apt/sources.list
Wx library installed/updated correctly.
But when I open the synaptic tool, and type the "codeblocks", I can only see the codeblocks 8.02 from Ubuntu official site. I have tried the alternative way( download many deb files from: http://apt.jenslody.de/pool/dbg/c/codeblocks/, then double click to install them), that not quite convenient way to install the debugger branch.

Any one can give me a hint? :)

I also run the "apt-get clear" and "apt-get update" many times.

Thanks.
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 ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5230
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: The 11 February 2012 build (7790) DEBUGGER BRANCH version is out.
« Reply #50 on: March 30, 2012, 04:53:25 am »
@jens:
I try to install your key, but failed. see the log:
Code: [Select]
[email protected]:~# sudo apt-get install jens-lody-debian-keyring
Reading package lists... Done
Building dependency tree      
Reading state information... Done
E: Couldn't find package jens-lody-debian-keyring

Maybe, this is the reason that I can't install codeblocks from apt-get.
any comments?
Thanks.

EDIT:
http://forums.codeblocks.org/index.php/topic,15024.msg100609.html#msg100609
This solve the problem.
« Last Edit: March 30, 2012, 06:14:55 am by ollydbg »
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.