I’m a Blonde by nature…
-
Here I’m, two weeks searching for some nasty problem in the very core of our system. The VS debugger already hates me. My boss probably hates me. The support guys definitely hate me. And the customers hate everybody. Ok, I found where the memory fails, and I even could fix the problem during the debug session, changing some values in the memory. But I can’t find what cause this problem!!! It’s so painfully to be stupid. :sigh:
The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word.
Have you tried using Data Breakpoints[^]? The debugger can automatically stop when a given memory location is changed. You probably have some stack- or heap-trashing bug, where you're overrunning a buffer, or possibly a calling-convention mismatch which can leave the stack unbalanced.
DoEvents: Generating unexpected recursion since 1991
-
Here I’m, two weeks searching for some nasty problem in the very core of our system. The VS debugger already hates me. My boss probably hates me. The support guys definitely hate me. And the customers hate everybody. Ok, I found where the memory fails, and I even could fix the problem during the debug session, changing some values in the memory. But I can’t find what cause this problem!!! It’s so painfully to be stupid. :sigh:
The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word.
Good luck
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest Hemingway -
Here I’m, two weeks searching for some nasty problem in the very core of our system. The VS debugger already hates me. My boss probably hates me. The support guys definitely hate me. And the customers hate everybody. Ok, I found where the memory fails, and I even could fix the problem during the debug session, changing some values in the memory. But I can’t find what cause this problem!!! It’s so painfully to be stupid. :sigh:
The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word.
The part I hate is how stupid you feel when you find the cause of the problem, and you want to beat yourself in the face with a 2x4. My most recent one went something like this:
TableEntry *entry = TableFind(device_serial_number);
if (entry == NULL) {
_DeviceTable.Add(new TableEntry(device_serial_number));
_DeviceList.InsertItem(entry->DeviceName);
}This piece of code only got exercised in unusual circumstances, and was an absolute PITA to figure out in release mode. I was down to link maps and assembly language listings before I found it. Then I had to go looking for a 2x4.
Software Zen:
delete this;
Fold With Us![^] -
Here I’m, two weeks searching for some nasty problem in the very core of our system. The VS debugger already hates me. My boss probably hates me. The support guys definitely hate me. And the customers hate everybody. Ok, I found where the memory fails, and I even could fix the problem during the debug session, changing some values in the memory. But I can’t find what cause this problem!!! It’s so painfully to be stupid. :sigh:
The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word.
Go get boundschecker or other error searching software. for my company it helped a lot to find very hard to find little bugs... Sometimes you are suprised how many errors this software can find.
bb |~ bb
-
Have you tried using Data Breakpoints[^]? The debugger can automatically stop when a given memory location is changed. You probably have some stack- or heap-trashing bug, where you're overrunning a buffer, or possibly a calling-convention mismatch which can leave the stack unbalanced.
DoEvents: Generating unexpected recursion since 1991
Thanks Mike, I actually have a hash map failure and I’m using the VS Memory Viewer, but I will take a look to the “Data Breakpoints”.
The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word.
-
Good luck
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest HemingwayI’ll need it, because I’m digging into a COM component with 410 MB source code /4704 source files/.
The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word.
-
The part I hate is how stupid you feel when you find the cause of the problem, and you want to beat yourself in the face with a 2x4. My most recent one went something like this:
TableEntry *entry = TableFind(device_serial_number);
if (entry == NULL) {
_DeviceTable.Add(new TableEntry(device_serial_number));
_DeviceList.InsertItem(entry->DeviceName);
}This piece of code only got exercised in unusual circumstances, and was an absolute PITA to figure out in release mode. I was down to link maps and assembly language listings before I found it. Then I had to go looking for a 2x4.
Software Zen:
delete this;
Fold With Us![^]Gary R. Wheeler wrote:
if (entry == NULL) { _DeviceTable.Add(new TableEntry(device_serial_number)); _DeviceList.InsertItem(entry->DeviceName); }
But of course entry is NULL, it will explode in the 2nd statement of the if.
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 4a out now (29 May 2008) -
Go get boundschecker or other error searching software. for my company it helped a lot to find very hard to find little bugs... Sometimes you are suprised how many errors this software can find.
bb |~ bb
It does to a certain extent, however as applications get complex its performance start going down to the extent that it is unusable.
Proud to be a CPHog user
-
It does to a certain extent, however as applications get complex its performance start going down to the extent that it is unusable.
Proud to be a CPHog user
Yes, but if you have automated test scenarios, or if you test small libraries it is very handy.
bb |~ bb
-
Have you tried using Data Breakpoints[^]? The debugger can automatically stop when a given memory location is changed. You probably have some stack- or heap-trashing bug, where you're overrunning a buffer, or possibly a calling-convention mismatch which can leave the stack unbalanced.
DoEvents: Generating unexpected recursion since 1991
Unless its a Managed application
Einstein argued that there must be simplified explanations of nature, because God is not capricious or arbitrary. No such faith comforts the software engineer. -Fred Brooks
-
I’ll need it, because I’m digging into a COM component with 410 MB source code /4704 source files/.
The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word.
-
I’ll need it, because I’m digging into a COM component with 410 MB source code /4704 source files/.
The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word.
Deyan Georgiev wrote:
410 MB source code
Is that right? Even if each line is full of 80 characters of source, that's 5.3 million lines. :~
-
Deyan Georgiev wrote:
410 MB source code
Is that right? Even if each line is full of 80 characters of source, that's 5.3 million lines. :~
Sorry my bad. The debug database and release files are in the same folder which I checked before. The reality is less then 50 Mb source code and about 1500 files. Did I mention that mentally I’m a blonde today?
The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word.
-
Sorry my bad. The debug database and release files are in the same folder which I checked before. The reality is less then 50 Mb source code and about 1500 files. Did I mention that mentally I’m a blonde today?
The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word.
I prefer to have blond days myself.
Need software developed? Offering C# development all over the United States, ERL GLOBAL, Inc is the only call you will have to make.
Happiness in intelligent people is the rarest thing I know. -- Ernest Hemingway
Most of this sig is for Google, not ego. -
Gary R. Wheeler wrote:
if (entry == NULL) { _DeviceTable.Add(new TableEntry(device_serial_number)); _DeviceList.InsertItem(entry->DeviceName); }
But of course entry is NULL, it will explode in the 2nd statement of the if.
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 4a out now (29 May 2008)Indeed it did. I've omitted a couple dozen lines of code from the original. This is what I got for copy/pasting code and not paying attention :doh:.
Software Zen:
delete this;
Fold With Us![^]