dfree confpars.c(648): free on null pointer.

[Niall O'Reilly]

On 22 Feb 2008, at 22:45, David W. Hankins wrote:

> I guess this is just a long winded way of explaining that we never
> knew multiple option name->code definitions ever worked, or at least
> were never intended to, and are equally surprised that anyone actually
> tried it that way.

	Good to know I'm not the only one to have fallen into this trap.

> I don't know if the code should or shouldn't permit this.  For the
> server it doesn't matter so much, but it's...weird...for the client,
> which has to dump options contents to dhclient.leases and format stuff
> into environment variables for dhclient-script.  I don't really want
> to make up my mind based off of what I think makes the prettiest api.

	I happen to know that someone has submitted a patch which
	causes an error message to be emitted whenever a second
	definition is encounterd for the same option code.

> I do know you shouldn't be seeing multiple free's, that's got to be
> a bug.

	IIUC, the redundant 'free' is due to incomplete clean-up
	after the conflicting option definition.  I don't know
	exactly where this is missing.


	Best regards,

	Niall O'Reilly
	University College Dublin IT Services

	PGP key ID: AE995ED9 (see www.pgp.net)
	Fingerprint: 23DC C6DE 8874 2432 2BE0 3905 7987 E48D AE99 5ED9



-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20080225/080dceab/attachment.bin>