Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: tromey@redhat.com
Cc: brobecker@adacore.com, gdb@sourceware.org
Subject: Re: "set foo"
Date: Tue, 27 Apr 2010 17:04:00 -0000	[thread overview]
Message-ID: <831ve0zv1a.fsf@gnu.org> (raw)
In-Reply-To: <m3tyqxk2t2.fsf@fleche.redhat.com>

> From: Tom Tromey <tromey@redhat.com>
> Cc: brobecker@adacore.com, gdb@sourceware.org
> Date: Mon, 26 Apr 2010 21:11:05 -0600
> 
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> For DWARF, GDB does two passes over the debuginfo.  The first time it
> >> reads "partial symbols".  There are some maint commands ("apropos partial")
> >> to dump this info, that might be helpful to you.
> 
> Eli> "maint info psymbols" indeed does not show "struct Lisp_Symbol", which
> Eli> was the reason I added "set Fmake_symbol" to .gdbinit.
> 
> One thing you could do is dump the dwarf for the CU holding Fmake_symbol.
> Then look for the definition of struct Lisp_Symbol.  Just those DIEs
> might be enough to see the problem.
> 
> Or you could dump all the dwarf and get it to me somehow.

Can GDB dump that?


  reply	other threads:[~2010-04-27 17:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-24 20:52 Eli Zaretskii
2010-04-24 21:21 ` Joel Brobecker
2010-04-25 13:40   ` Eli Zaretskii
2010-04-25 14:43     ` Joel Brobecker
2010-04-25 15:10       ` Eli Zaretskii
2010-04-26 16:24         ` Tom Tromey
2010-04-26 17:45           ` Eli Zaretskii
2010-04-26 17:51             ` Paul Koning
2010-04-26 19:46             ` Tom Tromey
2010-04-26 20:17               ` Eli Zaretskii
2010-04-27  3:11                 ` Tom Tromey
2010-04-27 17:04                   ` Eli Zaretskii [this message]
2010-04-27 17:25                     ` 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=831ve0zv1a.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --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