Ticket #73 (new defect)

Opened 2 years ago

Last modified 3 months ago

Passing csArray<>s across module boundaries is problematic

Reported by: res Owned by: admin
Priority: major Milestone:
Component: general Version:
Keywords: Cc:

Description

Migrated from SFbug:1496069.

Original description:
A number of interfaces take or return references to csArray<>s. This is problematic for memory tracking builds; csArray<>s have a different memory layout there (due the additional tracking information), hence, you cannot mix memtracking/non-memtracking modules once a csArray<> is involved in some interface.

Attachments

Change History

follow-up: ↓ 2   Changed 2 years ago by res

The real fix is to make the non-memtracking vs memtracking memory layout the same.

in reply to: ↑ 1   Changed 2 years ago by res

Replying to res:

The real fix is to make the non-memtracking vs memtracking memory layout the same.

...this will at least make const csArray<>s safe to use. For changeable arrays an iArray must still be used.

  Changed 1 year ago by sunshine

  • reporter changed from fossi to res

  Changed 3 months ago by jorrit

What is the status of this?

  Changed 3 months ago by res

Still not safe - csArray<> is fixed, but now CS::Memory::AllocatorMalloc has an additional member in MTI mode...

Add/Change #73 (Passing csArray<>s across module boundaries is problematic)

Author



Action
as new
 
Note: See TracTickets for help on using tickets.