Re: Questions about gnu debug
I almost took this to talk list except for one comment that re-iterates the need for something like cygwin with windoze, On 12/24/09, Marc Girod wrote: > > > Eliot Moss wrote: >> >> And this may add a little to your understanding: >> > Few of which pertains to cygwin... > > Eliot Moss wrote: >> >> Hope these distinctions help >> > They are matters of taste, and of experience. > I have an other taste and an other experience. > Hard to compare, I know. > > Eliot Moss wrote: >> >> emacs is an *editor* [...] but it would >> probably still feel somewhat primitive compared >> to advanced GUI interfaces. >> > Ahum. > Emacs is an environment which builds upon the generic concept of text > buffer. > This is a very powerful concept, because it allows for rich tool support, > and for in-depth and relatively light-weight user configuration. By > comparison, windows offer little support and a high threshold for users to > produce useful tools. > Humans painted on cave walls 3 years ago. Then they invented language. I wouldn't underestimate the importance of this observation. The existence of a tractable alphabet has been a big plus for communicating information, especially information suited to a computer. > GUIs have so far proven a temporary re-play of history for people who didn't > record it. Well, they do have their uses but tend to be expensive and confining. I'd like to see a GEICO ad with Bill Gates, and maybe those guys from Digital Research LOL... There is a learning curve for vi but now I find myself in screen editors thinking "where are those funny commands?" > > Marc > -- -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Questions about gnu debug
Eliot Moss wrote: > > And this may add a little to your understanding: > Few of which pertains to cygwin... Eliot Moss wrote: > > Hope these distinctions help > They are matters of taste, and of experience. I have an other taste and an other experience. Hard to compare, I know. Eliot Moss wrote: > > emacs is an *editor* [...] but it would > probably still feel somewhat primitive compared > to advanced GUI interfaces. > Ahum. Emacs is an environment which builds upon the generic concept of text buffer. This is a very powerful concept, because it allows for rich tool support, and for in-depth and relatively light-weight user configuration. By comparison, windows offer little support and a high threshold for users to produce useful tools. Humans painted on cave walls 3 years ago. Then they invented language. GUIs have so far proven a temporary re-play of history for people who didn't record it. Marc -- View this message in context: http://old.nabble.com/Questions-about-gnu-debug-tp26904577p26917415.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Questions about gnu debug
Eliot Moss wrote: And this may add a little to your understanding: Note these two options to gdb also... --tui Use a terminal user interface. -w Use a window interface. --tui will utilize a *curses interface -w brings up insight on my system -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Questions about gnu debug
And this may add a little to your understanding: gdb is a reasonable debugging tool, but is *command line* oriented. By itself, it provides no GUI interface. If you compile with -g then the available symbols let you talk about (non-local) variables, code locations, etc. emacs is an *editor* that can provide a somewhat GUI-like interface to gdb, by interpreting line numbers coming from gdb and positioning an editor cursor on the indicated line (good for stepping, etc.). And so forth. That is, emacs and gdb can play together reasonably well, but it would probably still feel somewhat primitive compared to advanced GUI interfaces. Eclipse can provide a good GUI interface, perhaps not quite as well integrated for C/C++ as for Java, but I understand it is pretty good. As stated before, it might be a little finicky to set up. Again, I believe it is calling gdb underneath. Hope these distinctions help.Eliot Moss -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Questions about gnu debug
Marco Atzeri wrote: --- Gio 24/12/09, Liming ha scritto: Thanks. Csaba, I still not so clear about gdb, I am usually use microsoft Visual Studio 1. With g++ -g -o executable_name a.o b.o ... Can I set break point? or this one only display the place the code has problem, then go to there to modify it? http://www.unknownroad.com/rtfm/gdbtut/gdbtoc.html 2. For ddd, Emacs, Eclipse Are they IDC with debug inside and can set break point? I just wondering if there has a software like Visual Studio IDE, so I can debug it inside it. ddd or insight will provide you with a GUI interface to gdb, that will be as close to what you're used to that you will be able to get. gdb, ddd, insight will provide breakpoints and the other things that you are used to . -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Questions about gnu debug
--- Gio 24/12/09, Liming ha scritto: > Thanks. Csaba, > > I still not so clear about gdb, I am usually use microsoft > Visual Studio > > 1. With g++ -g -o executable_nameĀ a.o b.o ... > Can I set break point? or this one only display the place > the code has problem, then go to there to modify it? > http://www.unknownroad.com/rtfm/gdbtut/gdbtoc.html > 2. For ddd, Emacs, Eclipse > Are they IDC with debug inside and can set break point? I > just wondering if there has a software like Visual Studio > IDE, so I can debug it inside it. > > --- On Wed, 12/23/09, Csaba Raduly 1) don't quote other email address. Spammers like to receive fresh address. 2) don't post on top. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? Marco -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Questions about gnu debug
Thanks. Csaba, I still not so clear about gdb, I am usually use microsoft Visual Studio 1. With g++ -g -o executable_name a.o b.o ... Can I set break point? or this one only display the place the code has problem, then go to there to modify it? 2. For ddd, Emacs, Eclipse Are they IDC with debug inside and can set break point? I just wondering if there has a software like Visual Studio IDE, so I can debug it inside it. --- On Wed, 12/23/09, Csaba Raduly wrote: > From: Csaba Raduly > Subject: Re: Questions about gnu debug > To: cygwin@cygwin.com > Cc: linhai...@yahoo.com > Date: Wednesday, December 23, 2009, 5:56 PM > On Wed, Dec 23, 2009 at 6:48 PM, > Liming > wrote: > > I read the FAQ, but still very confused, please help. > > > > 1. > > I have a project written by C++, I want to debug it > under Cygwin. I > > know I can use g++ -g, but I think this is for a > single .cpp file. > > Hi Liming, > If you have a project with multiple C++ files, you can > compile each > C++ file with "g++ -g" into an object file (usually with .o > suffix). > Then you can link the object files together with ... "g++ > -g", like > this: > > g++ -g -o executable_nameĀ a.o b.o ... > > Then you have an executable with debug info, which you can > load with gdb. > > > How > > to debug a whole Project? Anyway to debug the project > inside a windows like editor? > > > > If you used Windows IDEs, GDB needs time to get used to. It > has an > extensive manual (search for "Debugging with GDB"). > > There are many GDB front-ends. I've been using ddd > successfully. It > has a Cygwin package, I think (under Devel). > > Emacs has gdb integration. It is a very powerful editor, > but takes a > long time to learn. > > Anther possibility is Eclipse (it has GDB integration too, > but a bit > of an overkill, really). But it's fiddly to set up because > it is a > Windows program and sometimes paths have to be translated > between > Windows format and Cygwin. > > Hope this helps, > Csaba > -- > Life is complex, with real and imaginary parts > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Questions about gnu debug
On Wed, Dec 23, 2009 at 6:48 PM, Liming wrote: > I read the FAQ, but still very confused, please help. > > 1. > I have a project written by C++, I want to debug it under Cygwin. I > know I can use g++ -g, but I think this is for a single .cpp file. Hi Liming, If you have a project with multiple C++ files, you can compile each C++ file with "g++ -g" into an object file (usually with .o suffix). Then you can link the object files together with ... "g++ -g", like this: g++ -g -o executable_name a.o b.o ... Then you have an executable with debug info, which you can load with gdb. > How > to debug a whole Project? Anyway to debug the project inside a windows like > editor? > If you used Windows IDEs, GDB needs time to get used to. It has an extensive manual (search for "Debugging with GDB"). There are many GDB front-ends. I've been using ddd successfully. It has a Cygwin package, I think (under Devel). Emacs has gdb integration. It is a very powerful editor, but takes a long time to learn. Anther possibility is Eclipse (it has GDB integration too, but a bit of an overkill, really). But it's fiddly to set up because it is a Windows program and sometimes paths have to be translated between Windows format and Cygwin. Hope this helps, Csaba -- Life is complex, with real and imaginary parts -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Questions about gnu debug
I read the FAQ, but still very confused, please help. 1. I have a project written by C++, I want to debug it under Cygwin. I know I can use g++ -g, but I think this is for a single .cpp file. How to debug a whole Project? Anyway to debug the project inside a windows like editor? 2. The gnu C++ under Cygwin only support 32 bit windowss vista or 7. Is that right? Thanks! -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple