Re: Query object seg. faults on destruction...

[Warren Young]

Graham Reitz wrote:
> The output is different but it still crashes.  Although, this time the 
> crash is on the Row operator =.

If adding code moves the location of a crash, it's highly likely you've 
roached the heap, so the behavior can appear to change because the size 
of the executable is changing, thus moving things around in memory.  The 
underlying cause is probably still the same, and is probably neither 
~Query() nor Row::operator=(); they're just canaries in the coal mine.