User forums > Nightly builds

The 03 november 2006 build is out.

<< < (2/3) > >>

MortenMacFly:

--- Quote from: bdolter on December 12, 2006, 08:14:00 pm ---Has anyone else seen this???

--- End quote ---
Do you have setup a project or is this a single file (without project) you are trying to compile?
Could you provide us with a project (zipped) attached to a post and a step-by-step instruction how to reproduce? Because I can't.
With regards, Morten.
Ps.: Please don't hijack old forum threads.
Pps.: Note for the record: Within r3171+ were debugger changes that could be related.

bdolter:
Ok,

I've written some quick source to demostrate the problem.  Both app and dll are in the same workspace but differenct projects.  The idea is that a application would load a dll and retrieve a set of symbols at runtime.  For debugging the dll, I simply added the imports library to the link list and put ifdefs around the "GetProcAddress", this way I was able to debug the DLL up untill the Nov 3 build.

To Test, Load the Nov 2 Build.
load my workspace provided.
compile TestDLL, then TestAPP
set a break point in TestDLL, dllmain.c line 10 (I commented it). 
Now run TestApp in debug and you should get a break at line 10 of the DLL.

Now Load the Nov 3 (or later) build,
repeat, and you should get no breaks in the DLL.  You can set into the DLL, but no
break points will work.

For the record, where should I have posted this bug.  I didn't mean to "hijack" a thread.
Since this was bug that crept in between Nov 2 and Nov 3, I assumed the Nov 3 Nightly
build thread was the place to document it.

Brad


[attachment deleted by admin]

tiwag:
i can confirm this breakpoints issue,
even if the project is set up as targets (instead of using two projects) for app and dll it doesn't work for me.

[attachment deleted by admin]

MortenMacFly:

--- Quote from: tiwag on December 13, 2006, 10:32:57 am ---i can confirm this breakpoints issue,

--- End quote ---
Confirmed here, too. Already testing whether it's related to r3171 (which I don't think so though)...
With regards, Morten.

P.s.: Coming back to where to post: The problem I see that I personally focus on new messages because there are in general so many messages each day. So hijacking an *old* thread might result in being "ignored" although by mistake. I would have expected this as a new topic in the development forum. Surely with the advice that this happened during 2nd/3rd November. But it's alright just as it is... I didn't mean to be a nitpicker...

MortenMacFly:
OK - confirmed that it's related to the changes in r3171. If you uncomment them it'll work again properly. Unfortunately these changes (done by Yiannis) actually should avoid exactly that misbehavior. I need to talk to Yiannis about that...
With regards, Morten.

Ps:: As a QuickFix (for bdolter):
- goto the file debuggerstate.cpp
- search for the comment:

--- Code: ---// for foreign files, we still should use a relative path

--- End code ---
- remove (comment) the complete else section.

Navigation

[0] Message Index

[#] Next page

[*] Previous page