Search Results

The main reason for the seg fault is this string titleized_string = "";. As soon as you "set" titleized_string to "something-in-quotes" it becomes a constant. You cannot strcpy into a constant (it ha …

To clarify: the error /opt/sandbox50/bin/run.sh: line 31: 11290 .... is from check50, not from compile. It happens when check50 tests for "handles lack of argv[1]". That is because you do string k = a …

Your first order of business is finding out where it seg faults. valgrind is telling you it does, now you need gdb to tell you where. To get started with gdb: $ gdb ./server (gdb) break parse (gdb) …

Looks like a small memory leak in loookup. Maybe you're declaring a variable to store extension, but it's not allocated to include a null-terminator? The indexes function looks fine. I think index is …

This declaration char* request = ""; basically makes request a const char*, and as such is immutable. You should not "set" it to "", rather it needs to have some memory allocated before anything is co …

You are always using the subscript 'i'. 'i' has the value 3 when the first loop is finished. You can either change the subscript names in the y loop and the x loop OR just use 'i' again to run those l …

When you declare a string literal, as with char* php = "";,it is stored in read-only memory. So it is indeed seg-faulting here strcpy(php, path); because it cannot change read-only memory. Even if th …

There are problems in this index function. However, they are not causing all the check50 failures. Those problems probably stem from load function. Since check50 (probably) makes a direct request to c …

This hashtable[hash]->next = new_node; is a problem. hashtable is defined as an array of node pointers, not nodes. Therefore there is no such thing as hahstable[hash]->next. Maybe you meant hashtable[ …

Program never finds a jpg sig, so when it tries to fclose(img); it seg faults because img is NULL. Verify your "sig test". This (buffer[3]&0xf0)==0xe00) is wrong. (0xe00 is two bytes). But wait t …

What happens here else if (trav -> children[letter - 'a'] == NULL) if letter is apostrophe (ascii 39)?

This would work if no element of the values array is greater than 5. Since counts is initialized to limit, it has 5 elements, indexes 0 through 4. What happens here counts[values[i]-1]++; if values[i] …

The reason it does not give a seg fault under gdb is because of different memory usage than when it's run from the command line. The problem lies in the hash function. You might have started out with …

It looks like it will fail here else if (isalpha(argv) == 0) (I did not read the code further). argv is an array of strings. Review the man page for isalpha to be reminded that it takes a single cha …

This else block will execute exactly once (providing a jpeg sig is found in the input file): else//file not opened yet - { count++; char filena …