|List:||MySQL++||« Previous MessageNext Message »|
|From:||Warren Young||Date:||November 26 2007 2:53pm|
|Subject:||Re: Query object seg. faults on destruction...|
|View as plain text|
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.
|• Query object seg. faults on destruction...(ignore earlier posts please)||Graham Reitz||25 Nov|
|• Re: Query object seg. faults on destruction...||Graham Reitz||26 Nov|
|• Re: Query object seg. faults on destruction...||Warren Young||26 Nov|