Opened 11 years ago

Last modified 7 years ago

#862 closed defect (Fixed)

tor segfaults on sparc64

Reported by: ra Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version: 0.2.0.31
Severity: Keywords:
Cc: ra, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

i tried 0.2.0.31 and 0.2.1.7-alpha. both produce a bus error after a few seconds running on sparc64 gentoo linux.

[Automatically added by flyspray2trac: Operating System: Other Linux]

Child Tickets

Attachments (1)

bt.txt (2.0 KB) - added by ra 11 years ago.
backtrace

Download all attachments as: .zip

Change History (9)

comment:1 Changed 11 years ago by ra

both generate a BUS signal at connection_or.c:160
(see backtrace)

Changed 11 years ago by ra

Attachment: bt.txt added

backtrace

comment:2 Changed 11 years ago by ra

distribution (gentoo) bug report @ http://bugs.gentoo.org/show_bug.cgi?id=246483

comment:3 Changed 11 years ago by nickm

Looks like some kind of weird sparc64 alignment bug. Switching the code to use set_uint16(x,y) there instead of
*(uint16_t)(x) = y should fix stuff. I'll try patching it now.

comment:4 Changed 11 years ago by nickm

Does subversion revision r17262 fix this for you? If not, does it fail in the same way, or does it generate a
different backtrace?

comment:5 Changed 11 years ago by ra

r17262 works for me.
thanks for fixing this issue incredible fast! (:

comment:6 Changed 11 years ago by nickm

No problem; thanks for reporting the bug!

comment:7 Changed 11 years ago by nickm

flyspray2trac: bug closed.

comment:8 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.