From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: mark.kettenis@xs4all.nl, brobecker@adacore.com,
gdb-patches@sourceware.org
Subject: Re: New warning in GDB 7.5
Date: Mon, 20 Aug 2012 16:33:00 -0000 [thread overview]
Message-ID: <83a9xpcymx.fsf@gnu.org> (raw)
In-Reply-To: <20120820142417.GA1149@host2.jankratochvil.net>
> Date: Mon, 20 Aug 2012 16:24:17 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: eliz@gnu.org, brobecker@adacore.com, gdb-patches@sourceware.org
>
> On Sun, 19 Aug 2012 21:10:49 +0200, Mark Kettenis wrote:
> > set $tem = (struct Lisp_Symbol *) $ptr
> >
> > probably won't trigger a full symbol read since "struct Lisp_Symbol"
> > is a type and not a function or variable.
>
> It will, because GDB generates symbols for each type. See for example:
> process_structure_scope -> new_symbol_full <DW_TAG_structure_type> ->
> -> add_symbol_to_list
If it relies on DW_TAG_structure_type, it needs DWARF, perhaps even
newer than DWARF-2, doesn't it? Emacs debugging shouldn't depend on
that.
next prev parent reply other threads:[~2012-08-20 16:33 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 [this message]
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=83a9xpcymx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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