From: Marty McGowan <mcgowan@alum.mit.edu>
To: gdb@sourceware.org
Subject: Building on Darwin
Date: Tue, 21 Jun 2011 02:36:00 -0000 [thread overview]
Message-ID: <4E000397.6030601@alum.mit.edu> (raw)
Hi,
i'm trying to use gdb on my iMac
--------------
appleton:MM110605 applemcg$ ls -l /usr/bin/*cc
lrwxr-xr-x 1 root wheel 7 Mar 4 12:49 /usr/bin/cc -> gcc-4.2
-rwxr-xr-x 1 root wheel 287680 Oct 24 2010 /usr/bin/distcc
lrwxr-xr-x 1 root wheel 7 Mar 4 12:49 /usr/bin/gcc -> gcc-4.2
--------------
System Version: Mac OS X 10.6.7 (10J869)
Kernel Version: Darwin 10.7.0
Boot Volume: hd
Boot Mode: Normal
Computer Name: appleton
User Name: Marty (applemcg)
Secure Virtual Memory: Not Enabled
64-bit Kernel and Extensions: No
Time since boot: 14 days 5:50
--------------
i've used it successfully ( a prior version ) in the past on a ~ 32K
size C program and saw today for the first time the error message
reported in the "Building GDB on Darwin "
i followed the steps in "Creating a certificate", ran the codesign
command, and was treated with the same message:
Reading symbols from /Volumes/MM110605/src/eec/cummings...
warning: can't find section '__DATA.__common' in OSO file
/Volumes/MM110605/src/eec/compiler.o
warning: can't find section '__DATA.__common' in OSO file
/Volumes/MM110605/src/eec/dictionary.o
warning: can't find section '__DATA.__common' in OSO file
/Volumes/MM110605/src/eec/options.o
warning: can't find section '__DATA.__common' in OSO file
/Volumes/MM110605/src/eec/parserobj.o
warning: can't find section '__DATA.__common' in OSO file
/Volumes/MM110605/src/eec/word.o
done.
(gdb) run
Starting program: /Volumes/MM110605/src/eec/cummings
Unable to find Mach task port for process-id 95355: (os/kern) failure (0x5).
(please check gdb is codesigned - see taskgated(8))
(gdb)
I included the "cant find section ... " messages as I don't recall
seeing them in times past, and to offer any kind of clue.
I did have to go to the trouble of resetting my login keys in the
OS X, as i really have little idea of what's happening. i do get the
RSA, public key algorithm, but frankly what a certificate represents and
who is giving whom what and why escapes my ken.
in the btw department; i tried this repeatedly. in the first
instance, i created a 2K Certificates.p12 file (before resetting the
password, but i was successfully able to import into the System keychain
as recommended. that failed as well. then repeating the experiment,
but this time with (continue)^ nth, i received "unknown error" when the
certificate was being created. in this pass i offered no identity to
the certificate assistant. repeating a 4th or fifth time, but
supplying identity, i was able to export a *.pem file, which is just the
ascii email attachment. needless to say it was not effective.
is there a cookbook for this procedure? do i need to rebuild gcc?
Thanks,
--
-=*-+ Marty McGowan http://martymcgowan.tiddlyspace.com
next reply other threads:[~2011-06-21 2:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 2:36 Marty McGowan [this message]
2011-06-21 4:20 ` Joel Brobecker
2011-06-21 7:37 ` Tristan Gingold
2011-11-08 15:15 ` kidoshisama
2011-11-09 7:51 ` Tristan Gingold
2011-12-23 5:46 ` alanandersen1
2011-12-23 10:32 ` Tristan Gingold
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=4E000397.6030601@alum.mit.edu \
--to=mcgowan@alum.mit.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).