用addr造句子，“addr”造句

打印開始於內存地址 (addr)的字節Size的內存狀態，正如先前在應用程序編程接口部分所解釋的那樣。

打印關於addr單元內存的特殊細節，包括它的儲存單元（堆疊，累計，文本）以及，如果它累計了大量內存，還有它的分配調用鏈和釋放歷史。

Simulates reading size bytes starting at address addr, generates any purify errors that read would cause, and calls purify_stop_here upon error.

Prints specific details about the memory at location addr, including its location (stack, heap, text) and, if it is heap memory, then the call chains of its allocation and free history.

This requires DB2 to navigate down into the "addr" subtree of the document to look for phone elements at any level of the document. This is avoidable overhead.

這需要DB 2向下*到文檔的“addr ”子樹中，在文檔的任何級別上查找phone元素，而這本是可以避免的開銷。

模擬寫入開始於addr 的size字節，產生寫入將會導致的任何Purify錯誤，根據錯誤調用 purify_stop_here。

If MAP_FIXED is specified, addr must be a multiple of the pagesize.

模擬閲讀開始於addr的size字節，產生讀取將會導致的任何purify錯誤，根據錯誤調用purify_stop_here。