Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 73599
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 10, 20262026-05-10T20:13:37+00:00 2026-05-10T20:13:37+00:00

I have a dll that must be useable from C etc, so I cant

  • 0

I have a dll that must be useable from C etc, so I cant use string objects etc as a normal would, but I’m not sure on how to do this safely..

const char *GetString() {     std::stringstream ss;     ss << 'The random number is: ' << rand();     return ss.str().c_str(); } 

could the c string be destroyed when ss falls off the stack? I’m assuming so…

Another option may be to create a new string on the heap, but what is going to deallocate that?

const char *GetString() {     std::stringstream ss;     ss << 'The random number is: ' << rand();     char *out = new char[ss.str().size()];     strcpy(ss.str().c_str(), out);     return out;//is out ever deleted? } 

The same goes for pointers to other things as well as strings.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. 2026-05-10T20:13:37+00:00Added an answer on May 10, 2026 at 8:13 pm

    The first variant doesn’t work because you’re returning a pointer into a stack object, which will get destroyed. (More presisely, you return a pointer to a heap memory, whch will have been deleted().) Worse still, it may even work for some time, if nobody’s overwriting the memory, making it very hard to debug.

    Next, you can not return a const char* unless you return a pointer to a static string like this:

    const char *GetString() {     return 'a static string in DATA segment - no need to delete'; } 

    You second variant has the problem of returning memory allocated with new() into a C program that will call free(). Those may not be compatible.

    If you return a string to C, there are 2 way to do that:

    char *GetString() {     std::stringstream ss;     ss << 'The random number is: ' << rand();     return strdup( ss.str().c_str() ); // allocated in C style with malloc() }  void foo() {     char *p = GetString();     printf('string: %s', p));     free( p ); // must not forget to free(), must not use delete() } 

    or:

    char *GetString(char *buffer, size_t len) {     std::stringstream ss;     ss << 'The random number is: ' << rand();     return strncpy(buffer, ss.str().c_str(), len); // caller allocates memory }  void foo() {     char buffer[ 100 ];     printf('string: %s', GetString(buffer, sizeof( buffer ))); // no memory leaks } 

    depending on you memory handling policy.

    As a rule, you can NOT ever return a pointer or a reference to an automatic object in C++. This is one of common mistakes analyzed in many C++ books.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a dll that was written in c++, I need to use this
I have a DLL that I want to profile.. I tried to use Very
I have a C++ Builder DLL that must link against a Delphi package (BPL),
I have a DLL that needs to operate large ammounts of memory and must
I have a dll that contains a dot net assembly - common intermediate language.
I have a dll that contains a templated class. Is there a way to
Currently we have a DLL that checks whether a username/password is a valid Windows
I have written a DLL that uses MS Word to spell check the content
I have a VB6 dll that is trying to create a COM object using
I have a managed dll that calls into a native library. This native library

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.