Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jack Howarth <howarth@bromo.med.uc.edu>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Paul Pluzhnikov <ppluzhnikov@google.com>, gdb@sourceware.org
Subject: Re: [ANNOUNCEMENT] GDB 7.0 release process created
Date: Sun, 20 Sep 2009 17:36:00 -0000	[thread overview]
Message-ID: <20090920173607.GA18628@bromo.med.uc.edu> (raw)
In-Reply-To: <20090920171154.GT7961@adacore.com>

On Sun, Sep 20, 2009 at 10:11:54AM -0700, Joel Brobecker wrote:
> 
> That's what I suggested we do a few days ago, before we cut the branch.
> But I haven't had a chance to test this much. Right now, AdaCore has
> a separate branch for x86-darwin GDB, that we used to develop the port.
> We're trying to move to gdb-7.0, but we haven't had time to complete
> the integration and until then, testing is difficult. I definitely
> plan on completing this part before 7.0 is out, however.
> 
> In the meantime, I'll see if I can reproduce Jack's issue with the
> latest sources.
> 
> -- 
> Joel

Just to be clear, if I add...

http://sourceware.org/ml/gdb-patches/2009-09/msg00430.htm

to gdb cvs on x86_64-apple-darwin, I still see the warnings...

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.

but I also see...

(gdb) break 4
Breakpoint 1 at 0x10000154c: file himenoBMTxpa.c, line 4.
(gdb) r
Starting program: /Users/howarth/a.out 
Unable to find Mach task port for process-id 154: (os/kern) failure (0x5).
 (please check gdb is setgid procmod)
(gdb) 

So it seems like breakpoints can be set but their is a setgid problem.
        Jack


  reply	other threads:[~2009-09-20 17:36 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
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 [this message]
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=20090920173607.GA18628@bromo.med.uc.edu \
    --to=howarth@bromo.med.uc.edu \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=ppluzhnikov@google.com \
    /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