unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 22502-done@debbugs.gnu.org
Subject: bug#22502: 25.0.90; emacs_backtrace.txt
Date: Sun, 31 Jan 2016 20:24:23 +0200	[thread overview]
Message-ID: <83oac11uaw.fsf@gnu.org> (raw)
In-Reply-To: <80877ad6-3180-4270-b0bb-8bc04d0959c6@default> (message from Drew Adams on Sun, 31 Jan 2016 09:00:54 -0800 (PST))

> Date: Sun, 31 Jan 2016 09:00:54 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> 
> This is with the Emacs 25.1 pretest -
> 
> Backtrace:
> 0000000400174400
> 000000040017449a
> 00000004000a609a
> 00000004000be186
> 00000004000beeb4
> 00000004001c4a18
> 0000000076d68000
> 0000000076d79055
> 0000000076d68c07
> 0000000076d9d940
> 000007fefeda51a7
> 
> 
> In GNU Emacs 25.0.90.2 (x86_64-w64-mingw32)
>  of 2016-01-30
> Windowing system distributor `Microsoft Corp.', version 6.1.7601
> Configured using:
>  `configure --prefix=/tmp/emacs --without-dbus --without-imagemagick
>  'CFLAGS=-O2 -fomit-frame-pointer -g0' 'LDFLAGS=-static-libgcc
>  -static-libstdc++ -static -s -Wl,-s''
                             ^^^^^^^^^
Whoever built that binary, stripped the symbols (see the "-s" switch
above), so any such reports are useless, as no one can ever do
anything with them.  Too bad.

Would the person who is building these binaries please refrain from
using switches that are hostile to debugging, such as
-fomit-frame-pointer and -s?

Closing.





  reply	other threads:[~2016-01-31 18:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-31 17:00 bug#22502: 25.0.90; emacs_backtrace.txt Drew Adams
2016-01-31 18:24 ` Eli Zaretskii [this message]
2016-02-01 14:31 ` Kaushal Modi
2016-02-01 15:12   ` Drew Adams
2016-02-01 19:23   ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83oac11uaw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22502-done@debbugs.gnu.org \
    --cc=drew.adams@oracle.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).