[Pvfs2-developers] failed assert in id_gen_safe_register()

[Scott Atchley]

Hi Sam,

Thanks for the heads up. Is it safe to use on both the client and  
server?

What is the best way to catch changes like this so I can keep bmi_mx  
up to date with CVS?

Thanks,

Scott

On Sep 7, 2007, at 4:04 PM, Sam Lang wrote:

>
> Hi Scott,
>
> You don't need to use id_gen_safe for your ids.  If you switch to  
> using id_gen_fast_register, it should fix the abort you're seeing.   
> The abort is caused by the gen_safe code not being initialized by  
> default on the server now, unless components actually need to use it.
>
> -sam
>
> On Sep 7, 2007, at 1:44 PM, Scott Atchley wrote:
>
>> Hi all,
>>
>> I am trying a fresh checkout of PVFS2 from this morning. I have a  
>> single server and a single client.
>>
>> As soon as the client connects, the server aborts. Using gdb, the  
>> server calls BMI_mx_post_send_list(). This function calls my  
>> common send function, bmx_post_send_common, which calls  
>> id_gen_safe_register().
>>
>> In that function, there is an assert which fails:
>>
>> (gdb)
>> 61      int id_gen_safe_register(
>> 62          PVFS_id_gen_t *new_id,
>> 63          void *item)
>> 64      {
>> 65          id_gen_safe_t *id_elem = NULL;
>> 66
>> 67          assert(s_id_gen_safe_table != NULL);
>> 68
>> (gdb) p s_id_gen_safe_table
>> $8 = (struct qhash_table *) 0x0
>>
>> Where is this table initialized? Is this something I need to worry  
>> about or is cvs broken?
>>
>> Thanks,
>>
>> Scott
>> _______________________________________________
>> Pvfs2-developers mailing list
>> Pvfs2-developers at beowulf-underground.org
>> http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
>>
>