Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 66592 - bad catalyst modules dont trigger helpful error messages
Summary: bad catalyst modules dont trigger helpful error messages
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Hosted Projects
Classification: Unclassified
Component: Catalyst (show other bugs)
Hardware: All All
: High normal (vote)
Assignee: Gentoo Catalyst Developers
URL:
Whiteboard:
Keywords: InVCS
Depends on:
Blocks:
 
Reported: 2004-10-06 19:06 UTC by SpanKY
Modified: 2005-01-13 13:44 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SpanKY gentoo-dev 2004-10-06 19:06:06 UTC
when developing new catalyst stuff modules, often times a little bit of bad code can get you stuck for hours

for example, refer to a variable which hasnt been defined and catalyst will smugly report:
!!! catalyst: could not complete build

no s**t it didnt complete, but WHY DIDNT IT

if the last try/except clause in /usr/bin/catalyst could dump out a traceback, either beautified or only if say DEBUG=1, that would go a very long way
Comment 1 Chris Gianelloni (RETIRED) gentoo-dev 2004-12-15 18:31:46 UTC
Maybe add a --debug option to catalyst?  I could definitely see it being a good idea for tracing out problems with a build.
Comment 2 John Davis (zhen) (RETIRED) gentoo-dev 2004-12-15 19:41:29 UTC
there already is one ... it just needs some implementation
Comment 3 John Davis (zhen) (RETIRED) gentoo-dev 2004-12-17 20:47:19 UTC
ok, fixed in CVS. the default error is to display the traceback, so have fun ;)
Comment 4 John Davis (zhen) (RETIRED) gentoo-dev 2004-12-17 20:47:32 UTC
bah, closing ..