Does current GDB work correctly woth gcc 3.3 (3.4)?

Does current GDB work correctly woth gcc 3.3 (3.4)?

[Michael Stather]

I already asked this several times before, but I got no answer:
Does the upcoming gcc work correctly with gcc 3.x gereated executables
or does the "ignore breakpoints in constructor" bug still exist.

If yes, when it´s estimated to be fixed?

I think all linux developers need this to work with gdb reliabely!

regards

Michael

Re: Does current GDB work correctly woth gcc 3.3 (3.4)?

[Ramana Radhakrishnan]

[-- Attachment #1: Type: text/plain, Size: 967 bytes --]

Hi,

> I already asked this several times before, but I got no answer:
> Does the upcoming gcc work correctly with gcc 3.x gereated executables
> or does the "ignore breakpoints in constructor" bug still exist.
>

A more polite question would work . I tried out your stuff with g++
version 3.2 as well as cvs head for today using gdb cvs head also.
Attached are the session logs. It works for me over here.It would be
better if you could do something like this.




> If yes, when it´s estimated to be fixed?

me thinks it is already fixed. Maybe I am using a wrong test case but one
would not know. . A proper test case would definitely help. So maybe you
can send a better test case and hope for a reply.


>
> I think all linux developers need this to work with gdb reliabely!
All C++ developers need this to work with gdb reliably would be a better
way of putting things.


>
> regards
>
> Michael
>

cheers
ramana


----
Ramana Radhakrishnan
Codito Technologies

[-- Attachment #2: session --]
[-- Type: application/octet-stream, Size: 2068 bytes --]

[ramana@numenor acolon]$ g++ --version
g++ (GCC) 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[ramana@numenor acolon]$ /gccbuild/gdbfresh/intelbuildhere/gdb/gdb --version
GNU gdb 2004-01-28-cvs
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
[ramana@numenor acolon]$ /gccbuild/gdbfresh/intelbuildhere/gdb/gdb a.out
GNU gdb 2004-01-28-cvs
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db library "/lib/tls/libthread_db.so.1".

(gdb) b A::A()
Breakpoint 1 at 0x804855d: file fail.cpp, line 18.
(gdb) r
Starting program: /home/ramana/comedi/unipune/acolon/a.out 

Breakpoint 1, A (this=0x80497f8) at fail.cpp:19
19	   bFlag = false;   // Here I want to place a breakpoint
(gdb) n
20	   num = 9;
(gdb) n
21	}
(gdb) n
main (argc=1, argv=0xbfffe9a4) at fail.cpp:14
14	  return 0;
(gdb) n
15	}
(gdb) n
0x42015574 in __libc_start_main () from /lib/tls/libc.so.6
(gdb) c
Continuing.

Program exited normally.
(gdb) q
[ramana@numenor acolon]$ cat fail.cpp
// File simpletest.cpp: g++ -g3 simpletest.cpp
class A
{
public:
   A();
private:
   bool bFlag;
   int  num;
};

int main(int argc, char *argv[])
{
  A* pA = new A;
  return 0;
}

A::A()
{
   bFlag = false;   // Here I want to place a breakpoint
   num = 9;
}


[-- Attachment #3: sessionlatest --]
[-- Type: application/octet-stream, Size: 1385 bytes --]

[ramana@numenor acolon]$ /gccbuild/gccfresh/installhere/bin/g++ --version
g++ (GCC) 3.5.0 20040128 (experimental)
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[ramana@numenor acolon]$ /gccbuild/gccfresh/installhere/bin/g++ -g3 -static fail.cpp
[ramana@numenor acolon]$ /gccbuild/gdbfresh/intelbuildhere/gdb/gdb a.out
GNU gdb 2004-01-28-cvs
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db library "/lib/tls/libthread_db.so.1".

(gdb) b A::A()
Breakpoint 1 at 0x8048271: file fail.cpp, line 18.
(gdb) r
Starting program: /home/ramana/comedi/unipune/acolon/a.out 

Breakpoint 1, A (this=0x80bf180) at fail.cpp:19
19	   bFlag = false;   // Here I want to place a breakpoint
(gdb) n
20	   num = 9;
(gdb) n
21	}
(gdb) n
main (argc=1, argv=0xbfffeaa4) at fail.cpp:14
14	  return 0;
(gdb) n
15	}
(gdb) n
0x0805ab53 in __libc_start_main ()
(gdb) c
Continuing.

Program exited normally.
(gdb) 

Re: Does current GDB work correctly woth gcc 3.3 (3.4)?

[Daniel Jacobowitz]

On Wed, Jan 28, 2004 at 07:13:36PM +0530, Ramana Radhakrishnan wrote:
> Hi,
> 
> > I already asked this several times before, but I got no answer:
> > Does the upcoming gcc work correctly with gcc 3.x gereated executables
> > or does the "ignore breakpoints in constructor" bug still exist.
> >
> 
> A more polite question would work . I tried out your stuff with g++
> version 3.2 as well as cvs head for today using gdb cvs head also.
> Attached are the session logs. It works for me over here.It would be
> better if you could do something like this.
> 
> 
> 
> 
> > If yes, when it´s estimated to be fixed?
> 
> me thinks it is already fixed. Maybe I am using a wrong test case but one
> would not know. . A proper test case would definitely help. So maybe you
> can send a better test case and hope for a reply.
> 
> 
> >
> > I think all linux developers need this to work with gdb reliabely!
> All C++ developers need this to work with gdb reliably would be a better
> way of putting things.

It is half-fixed.  Some constructors can be breakpointed, some (for
base classes) can not.  A proper fix is still being worked on.

A whole lot of GNU/Linux and C++ developers don't seem to be crippled
by this.  It's really not that hard to work around.  Set a breakpoint
by PC if necessary.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer