After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 499873 - Variable 'this' not found
Variable 'this' not found
Status: RESOLVED FIXED
Product: nemiver
Classification: Other
Component: general
trunk
Other Linux
: Normal major
: ---
Assigned To: Nemiver maintainers
Nemiver maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-27 02:45 UTC by Jonathon Jongsma
Modified: 2008-06-19 15:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
example run with NMV_LOG_DOMAINS="nmv-local-vars-inspector2.cc nmv-variable-utils2.cc" (23.04 KB, text/plain)
2008-02-17 03:46 UTC, Jonathon Jongsma
Details

Description Jonathon Jongsma 2007-11-27 02:45:43 UTC
I've been hitting this error occasionally since the new variable stuff landed:

|X|void nemiver::variables_utils2::update_a_variable(const nemiver::common::SafePtr<nemiver::IDebugger::Variable, nemiver::common::ObjectRef, nemiver::common::ObjectUnref>&, const Gtk::TreeView&, Gtk::TreeIter&, bool, bool):nmv-variables-utils2.cc:187:raised exception: could not find variable in inspector: this

|E|void nemiver::LocalVarsInspector2::Priv::on_func_arg_visited_signal(const nemiver::IVarWalkerSafePtr&):nmv-local-vars-inspector2.cc:576:caught exception: 'could not find variable in inspector: this'
Comment 1 Dodji Seketeli 2008-02-07 23:13:21 UTC
I am sorry I could haven't been able to reproduce this yet :-(
Comment 2 Jonathon Jongsma 2008-02-17 03:46:17 UTC
Created attachment 105414 [details]
example run with NMV_LOG_DOMAINS="nmv-local-vars-inspector2.cc nmv-variable-utils2.cc"

I don't know if this is enough, let me know if I should log additional domains
Comment 3 Jonathon Jongsma 2008-02-17 03:52:17 UTC
Oh, I forgot to mention: I had an idea: could this might be related to debugging programs with some optimization on?  Not sure if that makes any sense or not since I haven't looked into this at all yet.  But I have been using nemiver quite a bit over the weekend and I have been hitting this issue a lot.  It'd be nice to get this one fixed before the release.
Comment 4 Dodji Seketeli 2008-03-16 11:15:01 UTC
I have still never been able to reproduce this problem myself. I don't know if it can be related to optimisations being on. One thing is sure though, I never debug with optimisations on :-) To me, it is just asking for problems :-)

In any case it would be much appreciated to update this bug with any more hint we might have.

Cheers,

Dodji:
Comment 5 Dodji Seketeli 2008-06-19 15:02:51 UTC
Man, now I reproduce the problem, big time. I have been chasing it today. More on this a bit later.
Comment 6 Dodji Seketeli 2008-06-19 15:42:27 UTC
Okay, I hope this is now fixed in trunk by commit #844.

Please confirm on this bug if it is fixed for you, as the bug is by nature hard to reproduce.

Thanks.