digitalmars.D.announce - Fitting Ddbg into your environment
- Jascha Wetzel (13/13) Feb 23 2007 Please consider voting for your favorite GDB frontend:
- Sean Kelly (6/22) Feb 23 2007 It's great that you're doing this, but I wish I could provide more than
- Jascha Wetzel (5/30) Feb 23 2007 you can vote for multiple entries, now.
- Sean Kelly (4/9) Feb 23 2007 I guess that explains my surprise at seeing it in the list. I thought
- Jascha Wetzel (4/29) Feb 23 2007 oh and btw - Ddbg is a win32 tool, so unix frontends can't be
- Sean Kelly (6/9) Feb 23 2007 Ah, I guess that changes things. I don't use emacs much on Windows--I
- Bill Baxter (11/27) Feb 23 2007 Another vote for emacs. (EmacsW32 for windows is what I use currently:
- Bill Baxter (4/11) Feb 23 2007 Whoops sorry -- forgot about the Eclipse effort! Make that
- Sean Kelly (4/8) Feb 23 2007 emacs debugging is a bit primitive compared to full IDEs (it doesn't do
Please consider voting for your favorite GDB frontend: http://ddbg.mainia.de/ Here is why: i'm adding GDB CLI imitation to Ddbg to have short-term integration into common frontends. the Ddbg CLI will still be continued, because i think it's simpler than GDB syntax if you use the debugger manually. to avoid implementing unnessecary details of the GDB CLI, i won't bother trying to clone it's behaviour exactly. instead i'm being pragmatic here and just doing what's nessecary to make frontends happy. therefore i'll have to check a few of them to approach a stable subset of the GDB CLI we can live with. currently i'm doing this with codeblocks, which is what i'm using myself. others will follow depending on your demand.
Feb 23 2007
Jascha Wetzel wrote:Please consider voting for your favorite GDB frontend: http://ddbg.mainia.de/ Here is why: i'm adding GDB CLI imitation to Ddbg to have short-term integration into common frontends. the Ddbg CLI will still be continued, because i think it's simpler than GDB syntax if you use the debugger manually. to avoid implementing unnessecary details of the GDB CLI, i won't bother trying to clone it's behaviour exactly. instead i'm being pragmatic here and just doing what's nessecary to make frontends happy. therefore i'll have to check a few of them to approach a stable subset of the GDB CLI we can live with. currently i'm doing this with codeblocks, which is what i'm using myself. others will follow depending on your demand.It's great that you're doing this, but I wish I could provide more than one answer :-) I'd use Visual Studio on Windows, and obviously something else on Unix. emacs most likely, since that works everywhere, but some of the fancy Linux IDEs look pretty nice. Sean
Feb 23 2007
you can vote for multiple entries, now. visual studio was just a joke by a friend - it's not a GDB frontend, at least as long as there isn't a plugin that supports GDB that i don't know of... Sean Kelly wrote:Jascha Wetzel wrote:Please consider voting for your favorite GDB frontend: http://ddbg.mainia.de/ Here is why: i'm adding GDB CLI imitation to Ddbg to have short-term integration into common frontends. the Ddbg CLI will still be continued, because i think it's simpler than GDB syntax if you use the debugger manually. to avoid implementing unnessecary details of the GDB CLI, i won't bother trying to clone it's behaviour exactly. instead i'm being pragmatic here and just doing what's nessecary to make frontends happy. therefore i'll have to check a few of them to approach a stable subset of the GDB CLI we can live with. currently i'm doing this with codeblocks, which is what i'm using myself. others will follow depending on your demand.It's great that you're doing this, but I wish I could provide more than one answer :-) I'd use Visual Studio on Windows, and obviously something else on Unix. emacs most likely, since that works everywhere, but some of the fancy Linux IDEs look pretty nice. Sean
Feb 23 2007
Jascha Wetzel wrote:you can vote for multiple entries, now. visual studio was just a joke by a friend - it's not a GDB frontend, at least as long as there isn't a plugin that supports GDB that i don't know of...I guess that explains my surprise at seeing it in the list. I thought you knew something I didn't :-) Sean
Feb 23 2007
oh and btw - Ddbg is a win32 tool, so unix frontends can't be considered. however, there might be emacs users on windows. i know people who use vi on windows, so... :) Sean Kelly wrote:Jascha Wetzel wrote:Please consider voting for your favorite GDB frontend: http://ddbg.mainia.de/ Here is why: i'm adding GDB CLI imitation to Ddbg to have short-term integration into common frontends. the Ddbg CLI will still be continued, because i think it's simpler than GDB syntax if you use the debugger manually. to avoid implementing unnessecary details of the GDB CLI, i won't bother trying to clone it's behaviour exactly. instead i'm being pragmatic here and just doing what's nessecary to make frontends happy. therefore i'll have to check a few of them to approach a stable subset of the GDB CLI we can live with. currently i'm doing this with codeblocks, which is what i'm using myself. others will follow depending on your demand.It's great that you're doing this, but I wish I could provide more than one answer :-) I'd use Visual Studio on Windows, and obviously something else on Unix. emacs most likely, since that works everywhere, but some of the fancy Linux IDEs look pretty nice. Sean
Feb 23 2007
Jascha Wetzel wrote:oh and btw - Ddbg is a win32 tool, so unix frontends can't be considered. however, there might be emacs users on windows. i know people who use vi on windows, so... :)Ah, I guess that changes things. I don't use emacs much on Windows--I prefer UltraEdit. So whatever works then, really. As long as some sort of graphical front-end is an option and it doesn't crash constantly I'll be happy. Sean
Feb 23 2007
Jascha Wetzel wrote:Please consider voting for your favorite GDB frontend: http://ddbg.mainia.de/ Here is why: i'm adding GDB CLI imitation to Ddbg to have short-term integration into common frontends. the Ddbg CLI will still be continued, because i think it's simpler than GDB syntax if you use the debugger manually. to avoid implementing unnessecary details of the GDB CLI, i won't bother trying to clone it's behaviour exactly. instead i'm being pragmatic here and just doing what's nessecary to make frontends happy. therefore i'll have to check a few of them to approach a stable subset of the GDB CLI we can live with. currently i'm doing this with codeblocks, which is what i'm using myself. others will follow depending on your demand.Another vote for emacs. (EmacsW32 for windows is what I use currently: http://ourcomments.org/Emacs/EmacsW32.html It's based on more recent sources than the gnu.org versions.) Although I haven't used emacs for debugging in ages (these days it's all Visual Studio), but back in the day I always found it a decent way to use gdb. And it's what I use for editing all the time anyway. For a more GUI-ish front end, Code::Blocks seems like a good choice, given that it's probably the only Windows IDE right now that has any support for D. --bb
Feb 23 2007
Bill Baxter wrote:Jascha Wetzel wrote:Please consider voting for your favorite GDB frontend: http://ddbg.mainia.de/For a more GUI-ish front end, Code::Blocks seems like a good choice, given that it's probably the only Windows IDE right now that has any support for D.Whoops sorry -- forgot about the Eclipse effort! Make that "Code::Blocks and Eclipse are the only IDEs with any D support". --bb
Feb 23 2007
Bill Baxter wrote:Although I haven't used emacs for debugging in ages (these days it's all Visual Studio), but back in the day I always found it a decent way to use gdb. And it's what I use for editing all the time anyway.emacs debugging is a bit primitive compared to full IDEs (it doesn't do more than show you the source code and current line in a separate pane), but it's what I use at work so I'm kind of used to it :-)
Feb 23 2007