Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Ramana Radhakrishnan" <ramana.radhakrishnan@codito.com>
To: michaelstather@nuzi.de
Cc: gdb@sources.redhat.com
Subject: Re: Does current GDB work correctly woth gcc 3.3 (3.4)?
Date: Wed, 28 Jan 2004 13:31:00 -0000	[thread overview]
Message-ID: <48828.203.199.140.162.1075297416.squirrel@webmail.codito.com> (raw)
In-Reply-To: <20040128092756.EF962693A53@sinope.kasserver.com>

[-- 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) 

  reply	other threads:[~2004-01-28 13:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-28  9:27 Michael Stather
2004-01-28 13:31 ` Ramana Radhakrishnan [this message]
2004-01-28 14:51   ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48828.203.199.140.162.1075297416.squirrel@webmail.codito.com \
    --to=ramana.radhakrishnan@codito.com \
    --cc=gdb@sources.redhat.com \
    --cc=michaelstather@nuzi.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox