Bug 129291 - subdomain_parser doesn't set an error code when there's an error in the #include processing
Summary: subdomain_parser doesn't set an error code when there's an error in the #incl...
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: AppArmor (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Steve Beattie
QA Contact: Keiran Haggerty
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-19 07:36 UTC by Steve Beattie
Modified: 2006-01-24 22:23 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Beattie 2005-10-19 07:36:31 UTC 
[kryten simple_tests]$ cat includes_bad_include.sd
#
#=DESCRIPTION includes testing - non-existent include should fail
#=EXRESULT FAIL
#
/does/not/exist {
  #include <does-not-exist/does-not-exist>
}
[kryten simple_tests]$ /sbin/subdomain_parser -d < includes_bad_include.sd
Error: #include <does-not-exist/does-not-exist> not found. line 6 in stdin
[kryten simple_tests]$ echo $?
0
Comment 1 Steve Beattie 2005-11-21 23:07:10 UTC 
A fix for this made it in to the SLES9 SP3 candidates, I don't know if this will get fixed for SL10.
Comment 2 Steve Beattie 2006-01-24 22:23:13 UTC 
I believe it has been decided this won't be fixed for SL10. It is fixed in the CODE 10.