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 757514 - Inspect an Expression is broken and doesn't work
Inspect an Expression is broken and doesn't work
Status: RESOLVED DUPLICATE of bug 730160
Product: nemiver
Classification: Other
Component: general
0.9.x
Other Linux
: Normal normal
: ---
Assigned To: Nemiver maintainers
Nemiver maintainers
Depends on:
Blocks:
 
 
Reported: 2015-11-03 10:34 UTC by el
Modified: 2017-03-19 17:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Bug demonstration in "Inspect an Expression" dialog (440.17 KB, image/png)
2015-11-03 10:34 UTC, el
Details

Description el 2015-11-03 10:34:23 UTC
Created attachment 314716 [details]
Bug demonstration in "Inspect an Expression" dialog

Inspect an Expression is broken and doesn't work, as can be seen from the screenshot. The "Expression Monitor" still shows the value, but the Inspect an Expression dialog simply fails to display the actual information.

jonas@cyberman:~$ nemiver --version
0.9.5
jonas@cyberman:~$ gdb --version
GNU gdb (GDB) Fedora 7.9.1-19.fc22
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
jonas@cyberman:~$
Comment 1 Ignazio Sgalmuzzo 2017-03-19 16:11:15 UTC
It seems a duplicate of bug 730160: I tried with that bug's proposed patch and it shows correctly expression values.
Comment 2 Hubert Figuiere (:hub) 2017-03-19 17:06:42 UTC
*** This bug has been marked as a duplicate of bug 730160 ***