>>> "bat ERROR in lib/smartall.c:121 Failed ASSERT: nbytes >0"
>>
>> This particular message is generated because some calling method is
>> passing in a 0 to the SmartAlloc methods as the number of bytes to
>> allocate.  This is not allowed via an ASSERT condition at the top of the
>> actual smalloc() method in the smartall.c file.  I'd think that you'd
>> need to do some kind of trace to see where the problem is originating.
>
> Hm, the question is what should i trace and how? Bat, the director or
> something other?

The bat executable is the one that you'd trace to see what it is doing. 
I don't know how much info bat may put out if you run in some kind of 
debug mode but that may be enough assuming there is such a mode.  But I 
suspect you'll need to somehow find out what it's exactly doing that is 
causing it to try and allocate 0 bytes of memory.  If you can get a 
specific cause then the Bacula bug folks may be able to track it 
down/fix it easier.

hope this helps,


--tom



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users