how to change static char* and not lose mem ?

Hello ,...

im working on a patch to smser (smser.sf.net)project.
since i don't how the change of static char* = " ... " to char * Iam avoiding the change in the main program .

in the program there are sevral static char varibales that need to ne changed:

orignal code :

Code:

---

static char* CONFDIR = "/.centericq";

---

i wish to change it by a function so i do the next. // since diffrent users will run the program from diffrent places .

Code:

---

#include <pwd.h>
#include <errno>
#include <assert>

int change_path()
{
  char *path_to_home = NULL;
  char *temp;

  temp        = CONFDIR;
  path_to_home = get_home_dir();

  CONFDIR = (char *) malloc ( sizeof(char) * ( strlen(path_to_home) + strlen(temp) + 1));
  strcpy(CONFDIR,path_to_home);//copy the actual path to confdir
  strcpy(CONFDIR + strlen (path_to_home),temp);

  free(path_to_home);

  return 0;
}

char* get_home_dir()
{
  char *path = NULL;
  int size = 0;

  struct passwd *passwd; //read man file for getpuid() or

  passwd = getpwuid(getuid());
  size = strlen((passwd->pw_dir));
  path = (char *) malloc (sizeof(char) *  size);
  assert(path);
  strcpy(path, passwd->pw_dir); //will copy the home directory to path
  /*
    * maybe just returning the pw_dir ?
    */
  return path;
}

---

p.s.
im writing from the memory so maybe i wrote some small errors (but this is the genral idea).

is it the right attiude with code changes ? (to write small functions expect changing in the main program).

You're asking how you can change a static char variable?

You don't. Just don't make it static if you want to change it.

it is in the orignal code stated as static and i don't know what will heppen if i change the static char * something to char *

static in C is used for two things (and in C++ as well, but it has further uses in C++, which I'm not going into here):

Outside a function, static is used to tell the compiler "This is a local <something> in this object file, don't let anyone see it".

Inside a function, it essentially makes a variable "global", but still only visible to the function. What I mean by this is that normally, local variables are "auto", meaning that they are created when the function is called and destroyed when the function returns. By adding static, the variable stays in a permanent place in memory, whether the function is in use at the time or not.

Examples:

Code:

---

static int x = 47;

static char *str = "Some data";

int next_int(void)
{
  static int x = 0;  // This will be incremented, so function will return 1, 2, 3, ...
  x++;
  return x;
}

static int some_func(void)  ...  // This function can ONLY be used from source that can "see" this function, so you can't call it from a different .C file [1]

---

[1] This assumes that we don't have any include of .C files - it is possible to include .C files, but as a general rule, it's not good style.

--
Mats

You shouldn't need to. I think you're confusing static and const.
Static just means that memory for this variable is allocated in the global area of memory management (there's actually a lot more about static, but that's the general idea)

Leave the static in and compile your code, it should work. If not, post the ouput of the compiler here.

QuantumPete

and don't cast malloc() or Salem will punish you. :)

The 'static' just alters it's scope, so that other modules cannot see it.
Within the module, you can still reassign it to point to another place in memory.

Quote:

---

Originally Posted by cpjust

and don't cast malloc() or Salem will punish you. :)

---

Thnx i studied some thing new ..
now for the casting itself real nice post i found ( http://cboard.cprogramming.com/showthread.php?t=25799 ).

so i don't need to do the malloc at all (?) since if i try to use strcpy ill get sigsegv:

Code:

---

#include <stdio.h>
#include <pwd.h>
#include <errno.h>
#include <assert.h>

static char* CONFDIR = ".123";
static char* CONfy  = ".2";
char* get_home_dir();

int change_path()
{
  char *path_to_home = NULL;
  char *temp;

  temp        = CONFDIR;
  path_to_home = get_home_dir();

  //CONFDIR = malloc ( sizeof(CONFDIR) * ( strlen(path_to_home) + strlen(temp) + 1));
  strcpy(CONFDIR,path_to_home);//copy the actual path to confdir
  strcpy(CONFDIR + strlen (path_to_home),temp);
 
  return 0;
}

char* get_home_dir()
{
  char *path = NULL;
  int size = 0;

  struct passwd *passwd; //read man file for getpuid() or

  passwd = getpwuid(getuid());
  size = strlen((passwd->pw_dir));
    return passwd->pw_dir;
 }
 
 int main()
 {
        change_path();
       
        return 0;
 }

---

since CONFDIR is equalled to const string (?).

p.s.
Thnx about the casting ..

> so i don't need to do the malloc at all (?) since if i try to use strcpy ill get sigsegv:
Yes, you need the malloc, but you don't need to cast the pointer type.

If you're getting warnings about not being able to cast a void*, then that means you're using a C++ compiler to compile your C code. Either use 'new' for memory allocation, or fix which compiler you run.

As for the segfault, this is because you're trying to modify a "string constant". These are typically marked as read-only by the operating system. Any attempt to modify them (say strcpy) will immediately end your program.

Right, you don't need to cast malloc at all. It's because it returns a void pointer, which can be assigned to any other pointer without a cast. In K&R (the original) C, there was no such thing as a void pointer, so malloc() and calloc() and realloc() returned char * pointers, which needed to be casted. No longer.

Also, C++ doesn't allow assigning any old pointer to a void pointer without a cast.

You still need the malloc(), though. You can't strcpy() something to a string literal like ".123".

Might I suggest using this?

Code:

---

static char* CONFDIR = "~/.centericq";

---

Then you wouldn't have to change it . . .

using "~... " will result in error since this sign is changed by the shell and will not work fine in any one .

Yes, you're right, sorry.

Code:

---

strcpy(CONFDIR + strlen (path_to_home),temp);

---

That's the same as

Code:

---

strcpy(CONFDIR, temp);

---

moment i thouth that if i strcpy from ptr + some amout of bytes ill start with the offset i added

Code:

---

void fooman()
{
  char *foo;
  foo = malloc (sizeof(foo) * 5+ 1);
  strcpy(foo,"foobar");
  printf("%s",foo); // foobar
  strcpy(foo + 3,"bar");
  printf("%s","sal");//foosal
  free(foo);
}

---

am i wrong ?

Now, the way I would solve the "gethomedir" is to pass in a fixed size array with a size of MAX_PATH (include limits.h). That is the number of chars that the longest filename and path is allowed to be.

Code:

---

  foo = malloc (sizeof(foo) * 5+ 1);

---

This allocates, on a 32-bit system, 21 bytes. I expect you actually wanted to say:

Code:

---

  foo = malloc (sizeof(*foo) * 6+ 1);

---

I thik dwks means

Code:

---

strcpy(x + strlen(x), b);
// is the same as:
strcat(x, b);

---

Strcat will probably be a tiny bit more efficient unless you need to strlen the first string anyways (if you do need strlen of the first string, it's obviously good to avoid doing strcat later, which will count the chars in the string again).

--
Mats

--
Mats

i use this solution since i use the passwd->pw_dir and copy it to the begning of CONFDIR.
but the size of CONFDIR is bigger then passwd->pw_dir .

Quote:

---

Originally Posted by jabka

i use this solution since i use the passwd->pw_dir and copy it to the begning of CONFDIR.
but the size of CONFDIR is bigger then passwd->pw_dir .

---

Sorry, that comment was referring to your original method where you are first mallocing one string, then mallocing another chunk of memory for the longer string, and freeing the first string - I didn't realize the code had been changed in that respect.

--
Mats