Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: New warning in GDB 7.5
Date: Sat, 18 Aug 2012 21:01:00 -0000	[thread overview]
Message-ID: <837gsvewyh.fsf@gnu.org> (raw)
In-Reply-To: <20120818205543.GL2798@adacore.com>

> Date: Sat, 18 Aug 2012 13:55:43 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> > These come from the following 2 lines in src/.gdbinit:
> > 
> >   # Force loading of symbols, enough to give us VALBITS etc.
> >   set main
> >   # With some compilers, we need this to give us struct Lisp_Symbol etc.:
> >   set Fmake_symbol
> > The comments explain why they are needed.
> 
> Are these really doing anything?

Yes.  They force GDB to read the symbol table of a couple of object
files, so the symbols from those files are known to GDB.  That is
needed for several commands in the file to work right from the start
of the debugging session.

> Unless "main" and "Fmake_symbol" were settings

No, they are symbols (function names).

> I think the warning is actually correct: these commands have no
> effect.

They have a useful side effect.

> The warning was added to catch the situation where the wrong assignment
> operator was used.

Sigh.  I guess we will have to live with this annoyance, then.


  reply	other threads:[~2012-08-18 21:01 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 [this message]
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
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=837gsvewyh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.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