Memo's weird problem-tdesc & "abrupt change"

Source: Internet
Author: User

Recently, the tdesc descriptor was used as a parameter reference for transmission. The length of the descriptor is normal before it is passed, but the length of the descriptor is out of bounds immediately after it is referenced. For memo, I don't know why it is compiled? Why is the stack (data is allocated on the stack, So it's weird )? Or why?

XXX: transformutf8tounicodel (* Buf, & unicodestring );
Cleanupstack: pushl (unicodestring );
// Parse body

// A problem occurs after the reference is passed. The unicodestring is hbufc *
Cstatusesobject * statusesobject = iparseengine-> parsestatusesobjectl (* unicodestring );
Cleanupstack: popanddestroy (unicodestring );

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.