What is the right way to allocate data to pass to an FFI call?

by

Ideally you would use std::alloc::alloc because you can then specify the desired alignment as part of the layout:

pub unsafe fn alloc(layout: Layout) -> *mut u8

The main downside is that you need to know the alignment, even when you free the allocation.

It’s common practice to use a Vec as an easy allocation mechanism, but you need to be careful when using it as such.

  1. Make sure that your units are correct — is the “length” parameter the number of items or the number of bytes?
  2. If you dissolve the Vec into component parts, you need to
    1. track the length and the capacity. Some people use shrink_to_fit to ensure those two values are the same.
    2. Avoid crossing the streams – that memory was allocated by Rust and must be freed by Rust. Convert it back into a Vec to be dropped.

  3. Beware that an empty Vec does not have a NULL pointer!:

    fn main() {
    let v: Vec<u8> = Vec::new();
    println!("{:p}", v.as_ptr());
    // => 0x1
}

For your specific case, I might suggest using the capacity of the Vec instead of tracking the second variable yourself. You’ll note that you forgot to update pcb_buffer after the first call, so I’m pretty sure that the code will always fail. It’s annoying because it needs to be a mutable reference so you can’t completely get away from it.

Additionally, instead of extending the Vec, you could just reserve space.

There’s also no guarantee that the size required during the first call will be the same as the size required during the second call. You could do some kind of loop, but then you have to worry about an infinite loop happening.

More Related Contents:

  1. How do I convert a Rust closure to a C-style callback?
  2. How do I create a Rust callback function to pass to a FFI function?
  3. How do I pass a closure through raw pointers as an argument to a C function?
  4. Can a struct containing a raw pointer implement Send and be FFI safe?
  5. How can I specify linker flags/arguments in a build script?
  6. What are Rust’s exact auto-dereferencing rules?
  7. Why is a trait not implemented for a type that clearly has it implemented?
  8. How can I include a module from another file from the same project?
  9. What does “Sized is not implemented” mean?
  10. How do I implement a trait I don’t own for a type I don’t own?
  11. What makes something a “trait object”?
  12. Is it possible to use `impl Trait` as a function’s return type in a trait definition?
  13. Cannot borrow as immutable because it is also borrowed as mutable in function arguments
  14. What is the relation between auto-dereferencing and deref coercion?
  15. What is the return type of the indexing operation?
  16. How to do a binary search on a Vec of floats?
  17. Change enum variant while moving the field to the new variant
  18. I implemented a trait for another trait but cannot call methods from both traits
  19. When is it useful to define multiple lifetimes in a struct?
  20. Moved variable still borrowing after calling `drop`?
  21. What is the difference between Copy and Clone?
  22. Is it possible to have stack allocated arrays with the size determined at runtime in Rust?
  23. Temporary value is freed at the end of this statement [duplicate]
  24. Is there a way to combine multiple traits in order to define a new trait? [duplicate]
  25. How can I store a pattern in a variable in Rust?
  26. How to switch between Rust toolchains?
  27. What does “missing lifetime specifier” mean when storing a &str in a structure?
  28. Comparing every element in a vector with the next one
  29. How to repeat a static string at compile time
  30. How to concatenate static strings in Rust

Leave a Comment