> "Paul G." <pgarceau@...> writes:
> > > Then, there are some issues with C++ and g++/gdb. Seems most of
> > > them are gone with g++ 3.2.2/gdb 5.2.1.
> > Where might I find a list of these particular issues?
> Maybe on the gdb bug database (if it exists at all) ?
Think that is a valid point, "if it exists at all", I mean. Cygwin version of Insight does not
function in the same way that the Mingw tool called "gdb" does, so it is probably not a good
resource to consider.
As to gdb itself, specifically the Mingw tool, I have yet to see anything anywhere that
talks much about what the issues actually are where Mingw built "tool", gdb, is concerned.
> All I can say is
> that g++ up to v3.2.2 was practically unusable for me with wathever
> version of gdb.
> It ignored breakpoints on constructors (g++ v3 creates
> two kinds of contructors for some classes: one for normal construction
> and other for nested construction, i.e. when the constructor is called
> from a derived class' constructor). Template code makes gdb crazy,
> jumping to random places of source code again and again. It has
> difficulties for inspecting data ('this' was reported as 'unknown
> type'). From time to time it decides it's enough and terminates the
> application being debugged.
This last paragraph, by itself, is far more information about gdb than I have ever had
before when I've attempted to bring it up.
Thank you, Oscar.
> All this was gone after upgrading to 3.2.2. But maybe it is related
> with the nature of the project. I'm working on a different piece of
> code now.