From: Simon Marchi <simon.marchi@polymtl.ca>
To: Viesturs Veckalns <viesturs.veckalns@cern.ch>
Cc: gdb@sourceware.org
Subject: Re: GDB support: Couldn't find method
Date: Mon, 20 Aug 2018 15:03:00 -0000 [thread overview]
Message-ID: <a56d7f3eb88bb62ed9b0a71132c3eb70@polymtl.ca> (raw)
In-Reply-To: <3FAD73755234DA45BB9E7CAA811E9CB70102A57FD6@CERNXCHG73.cern.ch>
On 2018-08-08 07:14, Viesturs Veckalns wrote:
> Hello Simon,
> It turns out gdb does not know anything about class methods and nested
> classes loaded from the shared library:
>
> (gdb) ptype GetLevel(resultcode)
> type = struct CompoundHistoUnfolding::Level {
> <incomplete type>
> } *
> (gdb) ptype CompoundHistoUnfolding::Level
> There is no field named Level
>
> gdb can list members of class CompoundHistoUnfolding but does not know
> about classes interfaced with the #include directive:
>
> (gdb) ptype CompoundHistoUnfolding
> type = class CompoundHistoUnfolding : public TNamed {
> private:
> Python Exception <class 'gdb.error'> No type named TString.:
> std::map<TString, HistoUnfolding*, std::less<TString>,
> std::allocator<std::pair<TString const, HistoUnfolding*> > >
> aggrbackgroundMC;
> Python Exception <class 'gdb.error'> No type named HistoUnfolding*.:
> std::vector<HistoUnfolding*, std::allocator<HistoUnfolding*> >
> _vbackgroundhistos;
> Python Exception <class 'gdb.error'> No type named SampleDescriptor*.:
> std::vector<SampleDescriptor*, std::allocator<SampleDescriptor*> >
> _expsyssamples;
> std::vector<SampleDescriptor*, std::allocator<SampleDescriptor*> >
> _markedsyssamples;
> HistoUnfoldingTH2 *totalbackground;
> char _signal_title[64];
> ...
>
> How to proceed from this point?
> Viesturs
I tried this simple code, and everything works as expected:
---
class Outer
{
class Inner
{
int foo = 2;
public:
int getFoo() {
return foo;
}
};
public:
Inner getBar()
{
return Inner();
}
};
int main()
{
Outer o;
return o.getBar().getFoo();
}
---
(gdb) p o.getBar().getFoo()
$2 = 2
(gdb) ptype Outer::Inner
type = class Outer::Inner {
private:
int foo;
public:
int getFoo(void);
}
To continue investigating, I would need a minimal reproducer, because at
this point I can only do some very wild guessing.
Simon
next prev parent reply other threads:[~2018-08-20 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 11:48 Viesturs Veckalns
2018-08-08 0:27 ` Simon Marchi
2018-08-08 11:15 ` Viesturs Veckalns
2018-08-20 15:03 ` Simon Marchi [this message]
2018-08-20 15:13 ` Pedro Alves
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=a56d7f3eb88bb62ed9b0a71132c3eb70@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb@sourceware.org \
--cc=viesturs.veckalns@cern.ch \
/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