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 570818 - better error message for not-found types (and other errors)
better error message for not-found types (and other errors)
Status: RESOLVED OBSOLETE
Product: gobject-introspection
Classification: Platform
Component: g-ir-scanner
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gobject-introspection Maintainer(s)
gobject-introspection Maintainer(s)
: 572139 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-02-06 21:23 UTC by Colin Walters
Modified: 2018-02-08 11:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Colin Walters 2009-02-06 21:23:47 UTC 
We really need an at least slightly better developer experience than:

** WARNING **: Can't resolve type 'KeySym' for field Meta.KeyBinding.keysym
Aborting

I think for each symbol in the C AST we parse, we should keep track of file+line+column if we're not already.  Then for each ast.py object, keep track of its source(s) in the C AST.  Finally when we hit an error like this not found type (which should btw actually be caught in g-ir-scanner, not g-ir-compiler), we can output e.g.:

warning: foo.c:42: Unknown C symbol KeySym

Possibly add hyperlinks to live.gnome.org wiki for each error.
Comment 1 Colin Walters 2009-02-17 21:20:24 UTC 
*** Bug 572139 has been marked as a duplicate of this bug. ***
Comment 2 André Klapper 2015-02-07 17:14:33 UTC 
[Mass-moving gobject-introspection tickets to its own Bugzilla product - see bug 708029. Mass-filter your bugmail for this message: introspection20150207 ]
Comment 3 GNOME Infrastructure Team 2018-02-08 11:47:36 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gobject-introspection/issues/11.