All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Juergen Gross <juergen.gross@ts.fujitsu.com>,
	Dietmar Hahn <dietmar.hahn@ts.fujitsu.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Jan Beulich <JBeulich@suse.com>
Subject: Re: Hidden symbol when debugging hypervisor
Date: Wed, 30 Apr 2014 11:07:28 +0100	[thread overview]
Message-ID: <5360CB60.7000704@eu.citrix.com> (raw)
In-Reply-To: <5360C4D3.3010000@ts.fujitsu.com>

On 04/30/2014 10:39 AM, Juergen Gross wrote:
> On 30.04.2014 11:26, George Dunlap wrote:
>> On 04/30/2014 10:02 AM, Dietmar Hahn wrote:
>>> Hi,
>>>
>>> while debugging a vmcore with the crash tool I stumpled over a 
>>> little problem.
>>> I wanted to look at the "struct csched_private" of credit scheduler 
>>> and got
>>> the contents of the "struct csched_private" of credit2.
>>> The debug informations of the hypervisor contain 2 entries
>>>   <1><b185e>: Abbrev Number: 8 (DW_TAG_structure_type)
>>>      <b185f>   DW_AT_name        : (indirect string, offset: 0x9d8d):
>>> csched_private
>>> and
>>>   <1><c0677>: Abbrev Number: 25 (DW_TAG_structure_type)
>>>      <c0678>   DW_AT_name        : (indirect string, offset: 0x9d8d):
>>> csched_private
>>>
>>> The first is credit and the second credit2. It seems in the crash 
>>> command the
>>> second entry wins :-(.
>>>
>>> Maybe crash has the possibility somewhere to get access to the 
>>> second structure
>>> (I couldn't find it) but for simplicity it would be better to have 
>>> different
>>> names
>>> I think.
>>> Are there any reasons not to rename
>>> struct csched_private -> struct c2sched_private
>>> or whatever?
>>
>> No reasons at all -- the naming is an artifact of development. Feel 
>> free to
>> send a patch renaming it.
>
> I tried it once: 
> http://lists.xen.org/archives/html/xen-devel/2013-02/msg02255.html
>
> Jan didn't like it.

It looks like he was only thinking about backtraces, not about cscope or 
about debugging core dumps.  Jan, do you have another solution for 
those, or shall we go ahead and change the names?

  -George

  reply	other threads:[~2014-04-30 10:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30  9:02 Hidden symbol when debugging hypervisor Dietmar Hahn
2014-04-30  9:26 ` George Dunlap
2014-04-30  9:39   ` Juergen Gross
2014-04-30 10:07     ` George Dunlap [this message]
2014-04-30 10:21       ` Jan Beulich
2014-04-30 11:28         ` Andrew Cooper
2014-04-30 13:16           ` Jan Beulich
2014-04-30 14:08             ` Andrew Cooper
2014-04-30 14:16               ` Jan Beulich
2014-04-30 14:32                 ` Andrew Cooper
2014-04-30 14:49                   ` Jan Beulich
2014-04-30 14:57                     ` George Dunlap
2014-04-30 15:23                       ` Jan Beulich
2014-04-30 14:58                     ` Andrew Cooper
2014-04-30 10:10     ` Jan Beulich

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=5360CB60.7000704@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=dietmar.hahn@ts.fujitsu.com \
    --cc=juergen.gross@ts.fujitsu.com \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.