From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: RE: [Bluez-devel] textfile.c find_key
Date: Tue, 08 Nov 2005 20:55:20 +0100 [thread overview]
Message-ID: <1131479720.5544.6.camel@blade> (raw)
In-Reply-To: <CBBBD909D2D6D211B4700090273F9E6E04C49B64@polaris.hhn.com>
Hi Robert,
> Not sure if you are interested in this but in the file textfile.c,
> function find_key. If map is ever NULL the strstr will segment fault.
> An instance of this happening would be when the key file was empty.
> This might happen if a Linux Op was removing keys that were
> invalidated by a lost pairing. I feel that in general checking for a
> NULL is better than not.
how can map be NULL? Check "man mmap" about the return value of mmap().
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-11-08 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 19:28 [Bluez-devel] textfile.c find_key Robert Wlaschin
2005-11-08 19:55 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-08 20:22 Robert Wlaschin
2005-11-08 22:13 ` Marcel Holtmann
2005-11-08 23:52 Robert Wlaschin
2005-11-09 0:03 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1131479720.5544.6.camel@blade \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.