Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #1731

Closed (moved)
Open
Opened Jul 26, 2010 by Roger Dingledine@arma

tor misparses libevent 1.4.14b-stable on bsd

hm, Tor v0.2.2.14-alpha has a wrong message on startup: "Jul 26 03:43:56.451 [warn] Libevent version 1.4.14b-stable often crashes when running a Tor server with BSD variants. Please use the latest version of libevent (1.3b or later)" 1.4.x is newer than 1.3.x and it doesn't crash either :-)

In tor_decode_libevent_version() it says: /* Try the new preferred "1.4.11-stable" format. */ fields = sscanf(v, "%u.%u.%u%c", &major, &minor, &patchlevel, &c); if (fields == 3 || (fields == 4 && (c == '-' || c == '_'))) { return V(major,minor,patchlevel); } Perhaps the problem is that Tor doesn't know how to handle both a letter and a dash?

I don't know what strings are valid libevent versions, so this is best as Nick's bug.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.2.2.x-final
Milestone
Tor: 0.2.2.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#1731