Uploaded image for project: 'Embedded Software & Tools'
  1. Embedded Software & Tools
  2. EXT_EP-8922

Translate address family in SlNetIfNDK

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • Network Development Kit
    • NDK-244
    • 3.00.00
    • 3.30.00
    • Hide
      The translation of the family attribute of the socket address struct (from NDK -> SlNetSock and vice versa) in some APIs is missing:

      SlNetIfNDK_recvFrom
      * The caller can optionally pass a sock addr struct that should be filled in by the stack with the peer's info
      * The NDK fills in this struct within NDK_recvfrom with NDK value for family
      * But, the struct should have the SlNetSock value of family when the API returns

      SlNetIfNDK_sendTo
      SlNetIfNDK_connect
      * The caller passes a sock addr struct that contain's the peer's info t
      * The caller sets sa_family to an SlNetSock value and it is currently passed directly to the underlying NDK API as such
      * This should be translated to an NDK value before passing the struct to the NDK API.
      Show
      The translation of the family attribute of the socket address struct (from NDK -> SlNetSock and vice versa) in some APIs is missing: SlNetIfNDK_recvFrom * The caller can optionally pass a sock addr struct that should be filled in by the stack with the peer's info * The NDK fills in this struct within NDK_recvfrom with NDK value for family * But, the struct should have the SlNetSock value of family when the API returns SlNetIfNDK_sendTo SlNetIfNDK_connect * The caller passes a sock addr struct that contain's the peer's info t * The caller sets sa_family to an SlNetSock value and it is currently passed directly to the underlying NDK API as such * This should be translated to an NDK value before passing the struct to the NDK API.

      Translate address family in SlNetIfNDK

            syncuser TI User
            syncuser TI User
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: