Binder concept is based on unique binder-token id. So no ids can be same.
Happening of which is a bug.
Please correct me if i am wrong.
On Thursday, 25 October 2012 18:44:59 UTC+5:30, shunty wrote:
> Hi
>
> I am trying to fix a android kernel panic, which occurred by BUG call in
> function binder_get_ref_for_node() in binder.c. More specifically
>
> while (*p) {
> parent = *p;
> ref = rb_entry(parent, struct binder_ref, rb_node_desc);
>
> if (new_ref->desc < ref->desc)
> p = &(*p)->rb_left;
> else if (new_ref->desc > ref->desc)
> p = &(*p)->rb_right;
> else
> *BUG();*
> }
>
> According to my understanding it is not able to find a suitable node to
> insert in the rbtree. Can some one please tell why there is call to BUG(),
> Binder can handle this case and return from here by saying traction fail or
> something.
>
> Does this mean that there is some problem while deleting the reference of
> node?
>
> Any suggestions ?
>
> Regards
> Shunty
>
--
--
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-kernel
---
You received this message because you are subscribed to the Google Groups
"Android Linux Kernel Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to android-kernel+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
