Frank Rudolph
|
Re: Debug a project built on x86 target with IDE 4 in Windows?
|
Frank Rudolph
01/14/2008 7:05 PM
post4290
|
Re: Debug a project built on x86 target with IDE 4 in Windows?
Momentics and I have come to an uneasy truce.
This feels somehow tenuous, because my results have not been always consistent. I am taking GREAT pains to do this the
same way each time.
The lastest thing I have found is that when I get an error message saying something about no such file found or can't
establish the limits of the function xyz,..
I tried this:
First, when I told the configuration view where my source code resides, I gave it the location on the target system disk
where the source code existed. I moved it up to the head of the list. AND I SELECTED THE OPTION CHECK FOR MULTIPLE
FILES...(I think this was important!)
Then when I first encountered the no such file, when I tried to attach to the running file, I simply opened what I
thought the most likely copy of my main souce for this project, "SimpleDownload.c". Now before I do anything else, I try
to set a breakpoint in the code. Momentics then threw up a popup called "Select Source File" ---> There were three
copies of SimpleDownload.c. The one at the top was the one imported into the project. It had a .c icon in front of it.
The others had generic file icons in front of them. I selected the top one and the debug session proceeded as if I had
done everything right!!!!
Furthermore, every time I did this again, the Select Source File window popped up right away to ask me where my source
code resided. There must be some event that must happen to make the IDE go out and try to find source code. The code was
there in both my failure cases and my subsequent success cases to ask me to select the source file, but if I didn't
enter data in EXACTLY the right sequence and explicitly set a breakpoint, it appears that the IDE defaults for these
kinds of projects in assuming there is no source code.
It just seems that there are an awful lot of possibilities for Momentics that have some counterintuitive roadblocks
lying around them and the documentation doesn't really give a good step-by-step how-to tutorial for these cases.
If you guys see nothing wrong with what I've done, then for goodness sake, let's codify this methodology in a tutorial
so poor fools like me don't have to waste a week of trial and error efforts to "get er done".
Thanks for your patience
|
|
|