Also i tried using gdb for analysing the dump, the backtrace i got from gdb is the following:

#0  _int_malloc(av=0x7c75a0000030, bytes=208) at ./malloc/malloc.c:4122
#1  __GI___libc_malloc(bytes=208) at ./malloc/malloc.c:3336
#2  alloc::vec::Vec<T,A> as core::clone::Clone>::clone()
#3  reqwest::async_impl::request::Request::try_clone()
#4  reqwest::async_impl::request::RequestBuilder::try_clone()
#5  futures_util::stream::fold::Fold::poll()
#6  pact_verifier::utils::with_retries::{{closure}}()
#7  pact_verifier::pact_broker::HALClient::fetch::{{closure}}()
#8  pact_verifier::pact_broker::HALClient::navigate::{{closure}}()
#9  pact_verifier::fetch_pact::{{closure}}::{{closure}}()
#10 tracing::instrument::Instrumented<T>::poll()
#11 futures_util::stream::flatten::Flatten::poll_next()
#12 futures_util::stream::collect::Collect::poll()
#13 pact_verifier::fetch_pacts::{{closure}}::{{closure}}()
#14 pact_verifier::verify_provider_async::{{closure}}::{{closure}}()
#15 tracing::instrument::Instrumented<T>::poll()
#16 tokio::task::task_local::TaskLocalFuture<T,F>::poll()
#17 pact_verifier::verify_provider_async::{{closure}}()
#18 tokio::runtime::context::blocking::BlockingRegionGuard::block_on()
#19 tokio::runtime::context::runtime::enter_runtime()
#20 tokio::runtime::runtime::Runtime::block_on()
#21 pact_ffi::verifier::handle::VerifierHandle::execute()
#22 pact_ffi::error::panic::catch_panic()
#23 pactffi_verifier_execute()
#24 verify_via_broker_direct() at pactffi_nif.c:778
#25 verify_via_broker_direct() at pactffi_nif.c:713
#26 erts_call_dirty_nif() at beam/erl_nif.c:466
#27 erts_dirty_process_main() at beam/beam_common.c:280
#28 sched_dirty_io_thread_func() at beam/erl_process.c:8768
#29 thr_wrapper() at pthread/ethread.c:116
#30 start_thread() at pthread_create.c:447
#31 clone3() at clone3.S:78

ahh its the verifier code. Can you say reduce the amount of variables being passed in the example, and reproduce. I see that are broker creds, but also a file_path, which ideally you should only have one or the other. is this for any type of pact spec, transport type, or any? Thx

@Yousaf Nabi (pactflow.io) i think you were right, apparently its only happening with my erlang code that interacts with the rust library

I tested my code with just hardcoding it with values and it worked fine without segmentation fault, now I have to debug whats wrong with my NIF code FYI @Srijan Choudhary

Update: when i am trying to verify via broker, getting segmentation fault… not when verifying via local file

@Yousaf Nabi (pactflow.io) is the pactffi library functions thread-safe ?

@Yousaf Nabi (pactflow.io) finally fixed https://github.com/greyorange-labs/pact_erlang/pull/49, tests are passing for both mac and linux machines 😄