public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Andy Lutomirski <luto@amacapital.net>, Kui Zhang <kuizhang@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Segmentation fault on all golang executables
Date: Thu, 12 Jun 2014 11:41:09 -0700	[thread overview]
Message-ID: <5399F445.6060200@linux.intel.com> (raw)
In-Reply-To: <CALCETrWTx5j9mx-CeXJDUAXh8KqVhGqBK+gpOPgJS1hOgH5tmg@mail.gmail.com>

On 06/12/2014 11:38 AM, Andy Lutomirski wrote:
>>
>> 2. Write a dummy section table that contains a single empty section of
>> type SHT_DYNSYM.  Hopefully the Go runtime will then get far enough to
>> fail cleanly.  And they can go and write a real ELF parser or copy my
>> reference parser correctly.  (hpa, can you apply my patches to make
>> the reference parser 32-bit clean?)
> 

Could you resend it please?

> Sigh.
> 
> See attached.  It seems to work for me.  Can you test it?  It'll hurt
> performance for Go programs, but I don't feel too bad about that.
> 

If Google fixes Go, will that address the performance problem?

	-hpa



  reply	other threads:[~2014-06-12 18:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12 16:59 Segmentation fault on all golang executables Kui Zhang
2014-06-12 17:20 ` Andy Lutomirski
2014-06-12 17:26   ` Andy Lutomirski
2014-06-12 17:36     ` Andy Lutomirski
     [not found]     ` <CAKx2Y1kTuK2cCn_uhVMgU5SeLsjXzHcFRmds7LP7-QG8BMqAdA@mail.gmail.com>
     [not found]       ` <CALCETrXnXp45iRC1h=_pOYrvXPc=hrTYnnVgsUg+i9URVfJTow@mail.gmail.com>
2014-06-13  5:47         ` Kui Zhang
2014-06-13  5:51           ` H. Peter Anvin
2014-06-12 18:38   ` Andy Lutomirski
2014-06-12 18:41     ` H. Peter Anvin [this message]
2014-06-12 18:42       ` Andy Lutomirski
2014-06-12 18:48         ` H. Peter Anvin
2014-06-12 18:51           ` Andy Lutomirski
2014-06-12 19:11             ` H. Peter Anvin

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=5399F445.6060200@linux.intel.com \
    --to=hpa@linux.intel.com \
    --cc=kuizhang@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    /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