A couple of debugging questions...

[profoundwhispers]

1- Why can't I step inside __ASSERT_ALWAYS macros like I used to in CodeWarrior? When I press F5 while I'm on an __ASSERT_ALWAYS(...) statement it just jumps to the next line.

2- I created two projects, MyModel (DLL) and MyApp (S60 application). I then added MyModel.dll to the list of libraries to link to from MyApp's properties and called ExampleFuncString(). It works fine. However, breakpoints in any function of the DLL code are never reached automatically, it's like they don't exist. Meanwhile, if I actually step into the function code from MyApp, it does jump to MyModel's souce files!

Thank you,
Sammy

[anttij]

2- I created two projects, MyModel (DLL) and MyApp (S60 application). I then added MyModel.dll to the list of libraries to link to from MyApp's properties and called ExampleFuncString(). It works fine. However, breakpoints in any function of the DLL code are never reached automatically, it's like they don't exist. Meanwhile, if I actually step into the function code from MyApp, it does jump to MyModel's souce files!

Open the dll's CW project too. When the project is open, CW can step into the code.

[profoundwhispers]

I'm sorry, maybe I wasn't clear. I do that fine in CW; I'm failing to do so in Carbide.c++

[anttij]

You were clear, I just read your post too quickly. Sorry, don't know how to do this in Carbide.c++.

[mitts]

Did you check Carbide.c++ Help, "Debugging DLLs"?