summaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorcypherpunks <cypherpunks@torproject.org>2015-12-15 16:30:04 +0100
committerNick Mathewson <nickm@torproject.org>2015-12-15 11:52:00 -0500
commit07cca627eaab800d4874f3d0914d3cf7eaa601a9 (patch)
tree6fec11ee49f2c8fb086e3d60be3291b73fe790f9 /changes
parent254d63dabe0b89f83c4df0edb1daf719cc5d4ab7 (diff)
downloadtor-07cca627eaab800d4874f3d0914d3cf7eaa601a9.tar.gz
tor-07cca627eaab800d4874f3d0914d3cf7eaa601a9.zip
Fix backtrace compilation on FreeBSD
On FreeBSD backtrace(3) uses size_t instead of int (as glibc does). This causes integer precision loss errors when we used int to store its results. The issue is fixed by using size_t to store the results of backtrace(3). The manual page of glibc does not mention that backtrace(3) returns negative values. Therefore, no unsigned integer wrapping occurs when its result is stored in an unsigned data type.
Diffstat (limited to 'changes')
-rw-r--r--changes/bug178273
1 files changed, 3 insertions, 0 deletions
diff --git a/changes/bug17827 b/changes/bug17827
new file mode 100644
index 0000000000..04cd3b5977
--- /dev/null
+++ b/changes/bug17827
@@ -0,0 +1,3 @@
+ o Minor bugfixes (compilation):
+ - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix on
+ tor-0.2.5.2-alpha.