Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Klee Dienes <klee@MIT.EDU>
To: Paul Smith <psmith@gnu.org>
Cc: gdb@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: GDB w/ Mac OS cores: "no core file handler recognizes format"
Date: Fri, 31 Jan 2014 03:20:00 -0000	[thread overview]
Message-ID: <1C03BC66-B7A2-4219-BCF9-C74288F9348E@mit.edu> (raw)
In-Reply-To: <20140131020928.GY9810@adacore.com>

I wrote the core dump support for GDB while I was working at NeXT/Apple, and would be happy to help you if you want to fold it back into stock GDB.  There should still be a copyright assignment on file for the time period it was written (but a lot could have changed since then, so it’s worth checking).  You can also build the Apple GDB from the last sources released at http://opensource.apple.com/source/gdb/gdb-1344/ — the core dump support seems to be present but not quite right. 

On Jan 30, 2014, at 9:09 PM, Joel Brobecker <brobecker@adacore.com> wrote:

>> Unfortunately I can't get it to work at all; I always get this error:
>> 
>>  $ ./x86_64-darwin/bin/gdb -c core.54937 myprog
>>  GNU gdb (GDB) 7.6.2
>>   ...
>>  Reading symbols from myprog...Reading symbols from
>> myprog.dSYM/Contents/Resources/DWARF/myprog...done.
>>  done.
>>  "core.54937": no core file handler recognizes format
> 
> I don't think we support core files on this platform.
> 
> -- 
> Joel


  reply	other threads:[~2014-01-31  3:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1391120555.28742.307.camel@pdsdesk>
2014-01-31  2:09 ` Joel Brobecker
2014-01-31  3:20   ` Klee Dienes [this message]
2014-01-31  7:58     ` Matt Rice
2014-01-31 13:34       ` Klee Dienes
2014-01-31 18:18       ` Stan Shebs
2014-01-31 18:41         ` Paul Smith
2014-01-31 20:55         ` Joseph S. Myers
2014-01-31 21:10           ` Matt Rice
2014-01-31  9:50   ` 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=1C03BC66-B7A2-4219-BCF9-C74288F9348E@mit.edu \
    --to=klee@mit.edu \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=psmith@gnu.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