From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Prickliness of the "invalid byte code" stuff Date: Sat, 15 Jun 2019 14:36:41 +0200 Message-ID: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="84472"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jun 15 14:37:31 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hc7w2-000Lpq-Sk for ged-emacs-devel@m.gmane.org; Sat, 15 Jun 2019 14:37:31 +0200 Original-Received: from localhost ([::1]:60410 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hc7w1-0005RX-UT for ged-emacs-devel@m.gmane.org; Sat, 15 Jun 2019 08:37:29 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33725) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hc7vK-0005Qn-4M for emacs-devel@gnu.org; Sat, 15 Jun 2019 08:36:47 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hc7vJ-0001jv-6A for emacs-devel@gnu.org; Sat, 15 Jun 2019 08:36:46 -0400 Original-Received: from quimby.gnus.org ([80.91.231.51]:58698) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hc7vJ-0001jN-05 for emacs-devel@gnu.org; Sat, 15 Jun 2019 08:36:45 -0400 Original-Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=stories) by quimby.gnus.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hc7vF-0006Xg-Cc for emacs-devel@gnu.org; Sat, 15 Jun 2019 14:36:43 +0200 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEXoDwD+XQD+VQD+QwD+ lwT+TAD+OAD+awKIWcxFAAACcklEQVQ4jW1TQW4bMQzkKXeqNXQWDcHnLiG9wEDOlsD4GlSwet5i AX2/o7XbpEkEY9fgkBpyOEvb+b/zvI41uNh/0of44BCLHHt7B2zjeQx2tbaU+43eJY8VcbHc23Fe 9SBB2DmOtWrvTXHVeIRxS5RoyAeQUTG2f4CJmOZZYOkHjeftDNYVrFrtZRZ01XKlMTaEVw4c0Yvu QH65ehr7+c3sijZT1Z61uNNGvM58Fo+rdKmaVRP7dSPh4RgIc+yKCsC34DdU8GBxIQRXkdy09ZzC GGcS71EiwQmGSwr2qtcdCH4VJxc8akqIt6wntAoAt0OiVSr61zrn8+iTXCxewCASNZnOCRNCg4LI 2LsKUrVY1taSMHsqIbAbcmD5ltErxNW2SPQELfyKLbiAdkuFurlLcifi4udwBSutfdllT1IPngy9 CrtDMFMzqxnIYrKRLSVWzIcmLLkdKRbDRjHPHla/8upO7DHRUiATgHq9K49dDT+fkJUhYtICpSAJ SynCK56gRUUyWCDEiytiJgU9WBHnz2QJAdMSIIlOjcvBPBxCqQi81FKxpHZBsnOBJ9Bsegb6Wa0L 5ImGeWE2UiuxwRgZu0iogAar3wFNsefW5071EgTU2BMAaH2cnmy/5HCcvsZvmhMAcqfJNNUENcF+ 2SsMyFwnbrtVLzDMzn2mCAkN2dOEcprxMXagwZAYEF7r2YQDPpI7kG+p1NzAg69lqiXhDvQb5kNT oO9wCbqVOwfMlLU/Dng0Fd4H7G/n8b+lOeFfgOiJiPrrjmAtG71F6fF6hRXjdyTRx/PUlL/T5zg9 dazqc3hSlZP/GrDrIP0SWbY/XrkPcDa+1HsAAAAASUVORK5CYII= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 80.91.231.51 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:237671 Archived-At: One thing that I've always wondered about when building Emacs is that running Emacs instances then start to fail in odd ways: url-http-parse-headers: Invalid byte code in /home/larsi/src/emacs/trunk/lisp/emacs-lisp/cl-seq.elc [8 times] And it's almost always with this "invalid byte code" stuff. What does it mean, really? Is there some sanity check to ensure that you're not running an .elc file designed for a different Emacs build, or... something else? -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no