Opened 11 years ago

Last modified 7 years ago

#781 closed defect (User disappeared)

segfault in libz

Reported by: nirgal Owned by:
Priority: High Milestone:
Component: Core Tor/Tor Version: 0.2.0.29-rc
Severity: Keywords:
Cc: nirgal, nickm, arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I'm using Version: 0.2.0.30-2etch+1 from http://mirror.noreply.org/pub/tor

Jul 20 22:30:39 magnesium Tor[31470]: Your Tor server's identity key fingerprint is 'nirgal 05F2 1249 3535 17EB 6205 0CF3 B309 7392 3F61 5B1C'
Jul 20 22:30:51 magnesium Tor[31470]: We now have enough directory information to build circuits.
Jul 20 22:30:51 magnesium Tor[31470]: Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Jul 20 22:30:53 magnesium Tor[31470]: Tor has successfully opened a circuit. Looks like client functionality is working.
Jul 20 22:31:58 magnesium Tor[31470]: Performing bandwidth self-test...done.
Jul 20 22:32:23 magnesium Tor[31470]: Self-testing indicates your DirPort is reachable from the outside. Excellent.
Jul 23 07:11:00 magnesium kernel: [722001.420438] tor[31470]: segfault at 9ac7669c ip b7f9988e sp bf9c4850 error 4 in libz.so.1.2.3[b7f94000+13000]

I'm not sure that repport helps a lot...

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

Child Tickets

Change History (4)

comment:1 Changed 11 years ago by arma

What version of libz do you have?

Does it generate a core file? Probably it would be in your datadir, which I
think on etch is /var/lib/tor/

If so, apt-get install the tor-debug package too, and then

gdb /usr/bin/tor /path/to/core

See also
https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ReportBug

Thanks!

comment:2 Changed 11 years ago by nickm

Hello? Are you still there?

comment:3 Changed 11 years ago by nickm

flyspray2trac: bug closed.

comment:4 Changed 7 years ago by nickm

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