SEGFAULT with some versions of libevent

Bug #315652 reported by Eric Day
2
Affects Status Importance Assigned to Milestone
Gearman
Fix Released
High
Eric Day

Bug Description

With most 1.4x versions of libevent, the following bug can crop up.

(gdb) run
Starting program: /home/eday/bzr/fixes/gearmand/.libs/lt-gearmand
[Thread debugging using libthread_db enabled]
[New Thread 0x7f170680b730 (LWP 7608)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f170680b730 (LWP 7608)]
0x00007f17063eeed1 in event_add (ev=0xf06e38, tv=0x0) at event.c:717
717 const struct eventop *evsel = base->evsel;
(gdb) print *base
Cannot access memory at address 0x0

Originally reported by gilad on the IRC channel.

Related branches

Eric Day (eday)
Changed in gearmand:
assignee: nobody → eday
importance: Undecided → High
status: New → Confirmed
Eric Day (eday)
Changed in gearmand:
status: Confirmed → Fix Committed
Eric Day (eday)
Changed in gearmand:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.