Thread: Problem with libgcrypt

Post the code where you call that function.

Passing garbage pointers to a function will make it crash in that function.

I'd much rather that you:

a) learn to use a debugger, then you won't have to keep visiting forums every time you have some code crash.
Peter's gdb Tutorial: Breakpoints And Watchpoints
Learn a few basic command like
- set breakpoints (break)
- print variables (print)
- step into, over and out of functions (step, next, finish)
- print call stack (bt)
- navigate the stack (frame)
You can get quite a lot done with just those few commands.

b) if you have a large amount of code, then uploading it to say dropbox to allow more than one person to make a contribution (should they want to). Avoid sites which force signup or bombard you with ads and stupidly long timeouts just to download the file - people will lose interest.

Also, you need to give CLEAR instructions for building and testing, along with details of any pre-requisite libraries.

If we have to mess about guessing what libraries to install, how to build it, what the input is (both files, and interactive Q&A), then we'll just give up and you'll still be in the dark.

Finally, bear in mind that you're asking for free time. Debugging large amounts of unfamiliar code is time consuming, so don't expect people to spend tens of hours on just your problem. The most you could reasonably expect is that some will download, build and run the code (assuming clear instructions). With luck, someone might spot some easy fixes.

If not, step a) is your only safe long term bet (aside from paying someone to do it for you).