Trouble with Strings

Question

I am currently debugging a sizable program. When I come to the following line of code:

value->binary_string = value_it->binary_string.substr(range->msb->value, range->size);

The program does not behave correctly. Here value is a pointer to a struct with a member named binary_string with type std::string. When I reach this line while debugging, I see that:

value_it->binary_string = "00000000000000000000000000000111"
range->msb->value = 0
range->size = 32

After this line of code executes, value->binary_string is empty! I have even changed the line to

value->binary_string = value_it->binary_string

and it still fails!

When I reach this line while debugging, my program is using about 100 Mb of memory, so I don't think it is a memory issue (though I am running Valgrind as we speak to verify this). I am using Ubuntu 11.10, g++-4.6 and libstdc++6.

Has anyone encountered something like this before? I have no idea why my strings aren't working!

Thanks,

Sam

EDIT1:

The type of value is NumberInst, defined below:

typedef std::string String;

struct NumberInst
{
    unsigned size;
    bool signed_;
    String binary_string;
    bool valid;
    unsigned value;

    NumberInst();
};

EDIT2:

It looks like I've narrowed down the search a little bit. While debugging, I tried a few print commands:

print value_it->binary_string
"00000000000000000000000000000111"
print value_it->binary_string[31]
'1'
print value_it->binary_string.substr(0, String::npos)
""
print value_it->binary_string.substr(0, 1)
""

It seems that substr is not working properly in this context. However, when I tested substr in my main function, it seemed to work okay.

Answer 1

I've found that there are usually two common reasons when "strange" things like this happen:

1. You made a simple mistake and are just overlooking it.
2. Some sort of memory corruption.

To check the first reason carefully read the offending code and make a conscious decision to read what the code is doing and not what you think it should be doing. It is very easy to overlook obvious errors by assuming the code should be doing something it actually isn't, especially in code you've been looking at for a while. For example, a few months ago I was debugging something and was having an issue with a variable "magically" changing its value all of a sudden. Turns out I was just printing the wrong variable (duh!) and I would of caught this sooner if I had been reading what the code actually said.

Memory corruption is a harder beast to find as it could happen from any piece of code running anytime prior to when the issue shows up. Valgrind does not guarantee to find all forms of corruption, see this question for an example. Running in debug mode, setting memory watch points (if you know where the corruption always occurs) and other memory related tools might help as will reducing the problem to its minimal form...keep eliminating code being run a little at time until the corruption doesn't happen.