Closed GoogleCodeExporter closed 8 years ago
The debian package is compiled by the Debian utilities... I do not know how to
include the symbol table and distribute it with Debian package. Mutsutoshi, if
you can figure out how to do that, and if you can reproduce the problem, that
would be great ! Thanks !
Original comment by mom040...@gmail.com
on 27 Feb 2014 at 6:09
it is considered that regardless of the debian package, to be a good idea to
put the symbol information always.
It is to be able to investigate at any time.
append '-g' flag to Makefile.in.
|CFLAGS += -g ${INCFLAGS}
If, Debian package only, Maybe... will be added to the following rules.
|DEB_CFLAGS_MAINT_APPEND = -g
we are investigating in the reproduction problem waiting to segfault.
Original comment by mutsutos...@mixi.co.jp
on 27 Feb 2014 at 8:45
I am not sure how -g flag will affect the performance. Also, the structure of
the Debian package is quite strict, I am not sure that it has a place for the
symbols map. I'll investigate it later.
Original comment by mom040...@gmail.com
on 27 Feb 2014 at 8:51
By the way, if you are using the TURN server for TCP data relay (RFC 6062) then
Debian is not the best choice... CentOS 6.5 or ArchLinux or Fedora or BSD would
be much better. The problem with Debian is that it currently does not support
SO_REUSEPORT socket option and without that socket option RFC 6062 cannot be
implemented accurately and cleanly. In Debian, we use a rather dirty hack to
overcome that problem - see the function
ioa_create_connecting_tcp_relay_socket() with comments inside. So for a serious
production environment I'd recommend CentOS 6.5 (until Debian includes
SO_REUSEPORT).
Original comment by mom040...@gmail.com
on 27 Feb 2014 at 9:10
Oops!
's True! There is no SO_REUSEPORT!
socket.h
|/* To add :#define SO_REUSEPORT 15 */
I think migration to CentOS.
Thanks a bunch!
Original comment by mutsutos...@mixi.co.jp
on 27 Feb 2014 at 10:17
I checked the Debian package building process. The binaries are compiled with
-g -O2 flags - but after that they are stripped. This is why you see no symbol
table. We do not have control over that stripping process and I am not sure
whether we can do anything about that.
Were you able to reproduce the problem ?
Original comment by mom040...@gmail.com
on 28 Feb 2014 at 6:56
Fixed in 3.2.2.9
Original comment by mom040...@gmail.com
on 3 Mar 2014 at 4:25
Original issue reported on code.google.com by
mutsutos...@mixi.co.jp
on 27 Feb 2014 at 2:39