From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: brobecker@adacore.com, mark.kettenis@xs4all.nl,
gdb-patches@sourceware.org
Subject: Re: New warning in GDB 7.5
Date: Mon, 20 Aug 2012 18:56:00 -0000 [thread overview]
Message-ID: <83y5l9bdeo.fsf@gnu.org> (raw)
In-Reply-To: <87d32lh25h.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Cc: brobecker@adacore.com, mark.kettenis@xs4all.nl, gdb-patches@sourceware.org
> Date: Mon, 20 Aug 2012 12:03:06 -0600
>
> I rebuilt emacs with -gstabs and my test worked fine.
> I didn't try anything else.
The problem was described here:
http://lists.gnu.org/archive/html/emacs-devel/2010-04/msg01124.html
I can still reproduce it, even with GDB 7.5, with a binary of Emacs
24.0.90 (an early pretest of v24.1), which was compiled with GCC 3.4.2
on Windows with "-gdwarf-2 -g3". If I remove this line from .gdbinit:
set Fmake_symbol
I get this error:
D:\gnu\emacs-24.x\emacs-24.0.90\src>gdb ./oo-spd/i386/emacs.exe
GNU gdb (GDB) 7.5
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from D:\gnu\emacs-24.x\emacs-24.0.90\src\oo-spd\i386\emacs.exe...done.
warning: Expression is not an assignment (and might have no effect)
SIGINT is used by the debugger.
Are you sure you want to change it? (y or n) [answered Y; input not from terminal]
Environment variable "DISPLAY" not defined.
Environment variable "TERM" not defined.
.gdbinit:1333: Error in sourced command file: <<<<<<<<<<<<<<<<<<<
No struct type named Lisp_Symbol. <<<<<<<<<<<<<<<<<<<
This doesn't happen with the latest Emacs trunk (nor with several
other binaries I have that I tried), compiled with the same version of
GCC. So I guess this is some subtle problem that is sensitive to the
arrangement of symbols in the debug info or something.
next prev parent reply other threads:[~2012-08-20 18:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-18 20:03 Eli Zaretskii
2012-08-18 20:56 ` Joel Brobecker
2012-08-18 21:01 ` Eli Zaretskii
2012-08-18 21:49 ` Mark Kettenis
2012-08-19 2:46 ` Eli Zaretskii
2012-08-19 4:37 ` Joel Brobecker
2012-08-19 16:53 ` Eli Zaretskii
2012-08-19 18:07 ` Joel Brobecker
2012-08-19 18:27 ` Eli Zaretskii
2012-08-19 18:33 ` Joel Brobecker
2012-08-19 18:33 ` Mark Kettenis
2012-08-19 18:59 ` Eli Zaretskii
2012-08-19 19:11 ` Mark Kettenis
2012-08-19 19:44 ` Eli Zaretskii
2012-08-20 14:24 ` Jan Kratochvil
2012-08-20 16:33 ` Eli Zaretskii
2012-08-20 17:07 ` Jan Kratochvil
2012-08-20 17:35 ` Eli Zaretskii
2012-08-20 15:01 ` Tom Tromey
2012-08-20 16:34 ` Eli Zaretskii
2012-08-20 17:28 ` Tom Tromey
2012-08-20 18:03 ` Tom Tromey
2012-08-20 18:56 ` Eli Zaretskii [this message]
2012-08-20 19:22 ` Tom Tromey
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=83y5l9bdeo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=tromey@redhat.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox