- Create your debug configuration, pointing to the project and program you require.
- Ensure that you setup your LD_LIBRARY_PATH in your environment variables as necessary.
- (and here's the really important part) In the Debug Configuration, go to the 'Debugger' tab. You should see a groupbox called 'Debugger Options' containing (at least) two tabs: 'Main' and 'Shared Libraries'. On the 'Main' tab, ensure that you have 'Non-stop mode' and 'Automatically debug forked processes'. In order to get these abilities, you'll need to have both non-stop gdb and multi-process gdb
- As a side note, you may need to also have your debug configuration pointed to a custom gdbinit command file with the following line:
- set follow-fork-mode child
Monday, February 11, 2013
Debugging multiple processes and following the children in Eclipse Juno
I guess Eclipse has made it much easier in recent versions of Eclipse and CDT to debug multiple processes and have the debugger follow children. It was actually easier than I had thought it would be to get this functionality in Eclipse Juno. To do so, follow these steps:
Wednesday, February 06, 2013
Using key gestures with parameterized Commands in WPF is "broken"
Ok, it's not actually broken, it just doesn't work the way I wanted (or expected). Apparently, there's a very good article on why they don't work the way I expected. To be clear, the way I expected them to work was:
- Define the command as a static RoutedUICommand and set the keyboard / mouse gestures I wanted on the command's InputGestures collection.
- Use said command in MenuItems, Buttons etc.
- Automatically have keyboard / mouse bindings setup everywhere (including the nice shortcut text on menu items in context menus / menu bar menus)