Core Dump / Segmentation Fault

Ok, this code creates a segmentation falult where the comments indicate, i've tried everything to fix it... BUt i can't, and i have no idea hpow to fix it. I've seen things about allocating memory for this, but i'm not sure how this works.

Code:

---

int main(int argc, char *argv[]) {
        char  *sFileName,                // This is the name of the file to pass to gcc/g++
              *sFileExt,                //  and its file extension
              *sOutName,                // This is the name of the output file for gcc/g++ (-o)
...

        cout << "Makefile name: ";
        cout << "DEBUG:: Breakpoint 1" << endl;
        scanf("%s", &sOutName);                                // THIS IS [EDIT] NOT [\EDIT] WHERE THE SEGMENTATION FAULT IS
        cout << "DEBUG:: Breakpoint 2" << endl;
        sOutName = substr(sOutName, 0, (strchr(sOutName, '.')-sOutName));        // strip all extensions // THIS IS WHERE THE SEG. FAULT IS

---

When i do that, i get these:

Quote:

---

epile.cpp: In function `int main(int, char **)':
epile.cpp:64: incompatible types in assignment of `char *' to `char[256]'

---

Code:

---

  59:          cout << "Makefile name: ";
  60:          cout << "DEBUG:: Breakpoint 1" << endl;
  61:          //scanf("%s", &sOutName);
  62:          fgets( sOutName, sizeof( sOutName ), stdin );
  63:          cout << "DEBUG:: Breakpoint 2" << endl;
  64:          sOutName = substr(sOutName, 0, (strchr(sOutName, '.')-sOutName));      // strip all extensions

---

Dont use pointers to strings!

If you're using C++ why not just write a string class
or steal one from the college boards or something

steal apstring
I wrote one for my system
CString (original isn't it?)

Automatic resizing etc. Checks for outofbounds indexing and bad pointers (but I added HUGE amounts of debug code to actually check the whole program, not just where CString is used)