0

I am having problems with debug50 since when I pass the executable through it, it gives me a segfault in the strncasecmp line. But if I execute the program normally, it works fine. This happens also in other parts of my code when I follow this approach of char*. Anybody has a similar issue or can help? I put part of my lookup code that gives the segfault

const char* lookup(const char* path) {
const char* ext;

ext = strchr(path, 46);
// skip the dot
ext++;
// compare extension to return type
if (strncasecmp(ext, "css", 3) == 0)
{
    return "text/css";
}... etc, etc

.... Thanks!!

0

I finally got it... it was an error with update50 didn't have the updated environment. :-)

| improve this answer | |
  • Be sure to accept your answer (after the requisite 2 days). This would be helpful information for others, and accepted answers "bubble to the top"! – DinoCoderSaurus Oct 13 '16 at 14:21
  • The same thing is happening to me but unfortunately using update50 hasn't resolved it. Valgrind isn't showing any errors – tamj0rd2 Nov 5 '16 at 10:08

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .