From: Jack Howarth <howarth@bromo.med.uc.edu>
To: gdb@sourceware.org
Subject: Re: [ANNOUNCEMENT] GDB 7.0 release process created
Date: Sun, 20 Sep 2009 02:54:00 -0000 [thread overview]
Message-ID: <20090920025432.GA22104@bromo.med.uc.edu> (raw)
In-Reply-To: <announce.20090916221710.GK2362@adacore.com>
On Wed, Sep 16, 2009 at 03:17:10PM -0700, Joel Brobecker wrote:
> Hello,
>
> A quick message to announce that the GDB 7.0 branch has just been created.
>
> The prerelease snapshots will be available at:
>
> ftp://sourceware.org/pub/gdb/snapshots/branch/gdb.tar.bz2
>
> The sources are also accessible via CVS:
>
> cvs -d :pserver:anoncvs@sourceware.org:/cvs/src co -r gdb_7_0-branch gdb
>
> This announcement has also been posted on the GDB web site at:
>
> http://www.sourceware.org/gdb/
>
> --
> Joel
What exactly is that status of darwin support? I noticed that the behavior
of gdb trunk on x86_64-apple-darwin10 has changed. Now I find that when built
with...
./src/configure --disable-werror --build=x86_64-apple-darwin10 --target=x86_64-apple-darwin10 --target=x86_64-apple-darwin10 --prefix=/Users/howarth/gdb_cvs/dist
the resulting gdb produces the output...
[Macintosh-2:~] howarth% gcc-4.2 -O0 -g -c himenoBMTxpa.c
[Macintosh-2:~] howarth% gcc-4.2 -O0 -g -o ./a.out himenoBMTxpa.o
[Macintosh-2:~] howarth% /Users/howarth/gdb_cvs/dist/bin/gdb ./a.out
GNU gdb (GDB) 7.0.50.20090920-cvs
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-apple-darwin10".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /Users/howarth/a.out...
warning: dsym file UUID doesn't match the one in /Users/howarth/a.out
warning: section __DATA.__common not found in /Users/howarth/himenoBMTxpa.o
(no debugging symbols found)...done.
(gdb)
next prev parent reply other threads:[~2009-09-20 2:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 22:20 Joel Brobecker
2009-09-18 0:42 ` Tom Tromey
2009-09-18 0:49 ` Hui Zhu
2009-09-20 2:54 ` Jack Howarth [this message]
2009-09-20 3:50 ` Paul Pluzhnikov
2009-09-20 14:32 ` Joel Brobecker
2009-09-20 15:02 ` Paul Pluzhnikov
2009-09-20 15:28 ` Joel Brobecker
2009-09-20 16:14 ` Paul Pluzhnikov
2009-09-20 17:12 ` Joel Brobecker
2009-09-20 17:36 ` Jack Howarth
2009-09-20 17:40 ` Joel Brobecker
2009-09-20 18:37 ` Paul Pluzhnikov
2009-09-20 19:12 ` Jack Howarth
2009-09-20 20:22 ` Paul Pluzhnikov
2009-09-21 4:34 ` Joel Brobecker
2009-09-21 12:57 ` Jack Howarth
2009-09-21 13:36 ` Jonas Maebe
2009-09-21 13:46 ` Jack Howarth
2009-09-21 13:55 ` Jonas Maebe
2009-09-21 19:19 ` Jim Ingham
2009-09-22 12:59 ` Mark Wielaard
2009-09-22 13:30 ` Jonas Maebe
2009-09-22 14:31 ` Mark Wielaard
2009-09-22 15:56 ` Daniel Jacobowitz
2009-09-22 17:10 ` Jack Howarth
2009-09-22 17:34 ` Daniel Jacobowitz
2009-09-22 18:11 ` Mark Wielaard
2009-09-22 19:28 ` Tom Tromey
2009-09-21 13:26 ` Jack Howarth
2009-09-20 16:19 ` Paul Pluzhnikov
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=20090920025432.GA22104@bromo.med.uc.edu \
--to=howarth@bromo.med.uc.edu \
--cc=gdb@sourceware.org \
/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