Bug 762275 (GLUSTER-543)

Summary:	libglusterfs calls exit()
Product:	[Community] GlusterFS	Reporter:	Patrick Matthäi <pmatthaei>
Component:	core	Assignee:	Anand Avati <aavati>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0.0	CC:	chrisw, gluster-bugs, pavan, shehjart, vijay
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Patrick Matthäi 2010-01-14 18:54:34 UTC

Hello,

the glusterfs library calls a exit() in its code:

spec.lex.c:     exit( YY_EXIT_FAILURE );

Calling exit() in a library is not the prefered way, better it should return; with a proper return code.

The code ends up in this file:
usr/lib/libglusterfs.so.0.0.0

This issue exists in both, the 2.0.9 and the 3.0, release.

Please fix it in 2.0.10 and 3.0.1.

Cheers.

Comment 1 Anand Avati 2010-01-23 09:41:28 UTC

This is autogenerated code from FLEX and not code written by a developer. It lies in the autogenerated YY_FATAL_ERROR() macro.

What problem have you faced with the existence of the exit() call? It is not called because of a parsing error.

Avati

Comment 2 Shehjar Tikoo 2010-02-09 08:01:56 UTC

Patrick,

Did you get a chance to look at this?