[reSIProcate] Dum segfaulting when dns is unavailable

[Scott Zuk]

Hi,

I've found a problem with resiprocate that causes the stack to segfault when 
returning 503 errors caused by failed dns requests.  I've attached a short 
test program that demonstrates the failure.

Basically, the program continually loops creating a new dum, sending a 
registration to an address that needs to be resolved, then deleting the dum.  
The program runs indefinately without error if there is a configured network 
interface on the machine.  If there is no network available however (ifdown 
eth0 or similar on linux), the program loops a few times then segfaults.

I haven't figured out exactly what's wrong yet but valgrind is showing lots of 
errors.  The stack only seems to crash whenever 
TransactionState::processNoDnsResults is called to generate a "503 Service 
Unavailable" message.  The problem is also not specific to registration, 
sending subscription requests has the same effect.  It looks like someone's 
data is getting stomped somewhere between processNoDnsResults and the various 
Client Handlers.  Can anyone else reproduce this?

~Scott
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dnsSegvTest.cxx
Type: text/x-c++src
Size: 6617 bytes
Desc: not available
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20050113/a088518d/attachment.cxx>