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

On Sun, Sep 20, 2009 at 11:37:07AM -0700, Paul Pluzhnikov wrote:
> 
> This is not really related to GDB. Explanation (at least as far as I
> understand what's happening):
> http://sourceware.org/ml/gdb/2009-08/msg00085.html
> 
> On Sun, Sep 20, 2009 at 10:39 AM, Joel Brobecker <brobecker@adacore.com> wrote:
> 
> >    % sudo chgrp procmod gdb
> >    % sudo chmod g+s gdb
> 
> That appears to no longer be sufficient on Mac OS X 10.5.8 (at least
> it doesn't work for me):
> 
> $ ls -l gdb/gdb
> -rwxrwsr-x  1 ppluzhnikov  procmod  4416668 Sep 20 10:20 gdb/gdb
> $ gdb/gdb ./t
> GNU gdb (GDB) 7.0.50.20090920-cvs
> ...
> Reading symbols from /Users/ppluzhnikov/gdb-cvs/build/t...(no
> debugging symbols found)...done.
> (gdb) r
> Starting program: /Users/ppluzhnikov/gdb-cvs/build/t
> Unable to find Mach task port for process-id 39624: (os/kern) failure (0x5).
>  (please check gdb is setgid procmod)
> (gdb) q
> 
> 
> -- 
> Paul Pluzhnikov

I suspect if someone posts to llvm-dev (where a lot of the Apple dev tool
folks hang out) we might get a quick answer.
         Jack


  reply	other threads:[~2009-09-20 19:12 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
2009-09-20 17:40                 ` Joel Brobecker
2009-09-20 18:37                 ` Paul Pluzhnikov
2009-09-20 19:12                   ` Jack Howarth [this message]
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=20090920191211.GB19245@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