Skip to Content.
Sympa Menu

freetds - RE: asprintf vasprintf

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Castellano, Nicholas" <Nicholas_Castellano AT acml.com>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: RE: asprintf vasprintf
  • Date: Thu, 29 Aug 2002 13:00:58 -0400


The code is handling SIGSEGV, not ignoring it. It's perfectly legitimate
and portable to handle SIGSEGV as long as you either longjmp() back to a
saved state, or exit the process.

-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu]
Sent: Thursday, August 29, 2002 12:25 PM
To: TDS Development Group
Subject: [freetds] RE: asprintf vasprintf


I don't understand why all this talk about SIGSEGV handlers. From man 2
sigaction:

According to POSIX, the behaviour of a process is unde­
fined after it ignores a SIGFPE, SIGILL, or SIGSEGV signal
that was not generated by the kill() or the raise() func­
tions. Integer division by zero has undefined result. On
some architectures it will generate a SIGFPE signal.
(Also dividing the most negative integer by -1 may gener­
ate SIGFPE.) Ignoring this signal might lead to an end­
less loop.

Anything depending on handling SIGSEGV will be platform-dependent anyway.

--
berndfoobar AT users.sourceforge.net is probably better to bookmark than any
employer-specific email address I may have appearing in the headers.
Vanity page: http://www.tsct.co.za/~berndj/



The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not be
responsible for carrying out such orders and/or instructions. Kindly refrain
from sending orders or instructions by e-mail unless you have confirmed that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming e-mail
correspondence of staff members serving certain functions.






Archive powered by MHonArc 2.6.24.

Top of Page