[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bluetooth-dev] sending data and access violation in l2cap



Walter wrote:

> > the l2cap->frame is a pointer in the newly subscribed tx buf which points
> at the start of the l2cap > frame i.e the hci header is "stripped". It is
> set when you cast the tx_buffer to a l2cap_buf in :
> > l2cap_buf = (l2cap_tx_buf *)(tx->data). See header files for the details.
>
> Could this be replaces by:  l2cap_buf = (l2cap_tx_buf *)&tx->data; ?
>
> -
> To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
> the body of a message to majordomo@xxxxxxx.com

No. That will give you the address of the field which points to the buffer,
not the address of the buffer.

Are you seeing the problem in user mode? Can you use gdb to see the bad
address?

--Gordon

-
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com