BorlandTalk.com Forum Index BorlandTalk.com
Borland discussion newsgroups
 
Archives   FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Stopping the debugger in DllEntryPoint

 
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> C++ Builder (IDE)
View previous topic :: View next topic  
Author Message
Edward Diener
Guest





PostPosted: Sat Sep 13, 2003 12:17 pm    Post subject: Stopping the debugger in DllEntryPoint Reply with quote



Is there some esoteric reason why the integrated debugger can not stop in
the DllEntryPoint for a DLL or a BPL ? I set the breakpoint there, I have
the source for the file which contains the DllEntryPoint for a BPL in my
source path, yet when I run an EXE which loads the package the debugger
never stops there and the line on which I have set a breakpoint is green
instead of red. And yes the .tds is in the right place since the debugger
will stop at other breakpoints in my BPL.



Back to top
Ed Mulroy [TeamB]
Guest





PostPosted: Sat Sep 13, 2003 3:31 pm    Post subject: Re: Stopping the debugger in DllEntryPoint Reply with quote



What you are doing is surely more exotic than this.

Could you be debugging from within the EXE's project? Try from within the
BPL's.

I did a simple check using a project for a DLL that merely adds two numbers
and returns the result. When in the project for the DLL I did a Run|Project
and selected the EXE which loads it (implicitly linked - the import lib is
part of the EXE's project list). It stopped at the breakpoint on the return
statement in DllEntryPoint.

I hope this helps but fear your project is too complex to not have the EXE's
project active.

.. Ed

Quote:
Edward Diener wrote in message
news:3f630ad6$1 (AT) newsgroups (DOT) borland.com...

Is there some esoteric reason why the integrated debugger
can not stop in the DllEntryPoint for a DLL or a BPL ? I set
the breakpoint there, I have the source for the file which
contains the DllEntryPoint for a BPL in my source path, yet
when I run an EXE which loads the package the debugger
never stops there and the line on which I have set a
breakpoint is green instead of red. And yes the .tds is in the
right place since the debugger will stop at other breakpoints
in my BPL.




Back to top
Edward Diener
Guest





PostPosted: Sat Sep 13, 2003 4:19 pm    Post subject: Re: Stopping the debugger in DllEntryPoint Reply with quote



Ed Mulroy [TeamB] wrote:
Quote:
What you are doing is surely more exotic than this.

Could you be debugging from within the EXE's project? Try from
within the BPL's.

Thanks, Ed. I too noticed that if I am debugging the BPL, it will stop but
not when I am debugging an EXE which loads a BPL. I don't understand why it
will not stop in the latter case since it will stop in all other BPL code
from the EXE if I set the appropriate breakpoint in the BPL's source code.

Quote:

I did a simple check using a project for a DLL that merely adds two
numbers and returns the result. When in the project for the DLL I
did a Run|Project and selected the EXE which loads it (implicitly
linked - the import lib is part of the EXE's project list). It
stopped at the breakpoint on the return statement in DllEntryPoint.

I hope this helps but fear your project is too complex to not have
the EXE's project active.

No, I can go through the BPL's IDE and have the EXE run as the application.
That solves the problem, thanks. It does seem that if I am debugging the
EXE, it should be able to stop anywhere in a BPL ( or DLL ) as long as the
IDE finds the equivalent .tds and source file for the latter.




Back to top
Ed Mulroy [TeamB]
Guest





PostPosted: Sat Sep 13, 2003 6:44 pm    Post subject: Re: Stopping the debugger in DllEntryPoint Reply with quote

Quote:
... It does seem that if I am debugging the EXE, it should
be able to stop anywhere in a BPL ( or DLL ) as long as the
IDE finds the equivalent .tds and source file for the latter.

With td32 you could load the symbol table and go on from there. That is
what is needed here, but I could find no equivalent in the BCB IDE.

I'm sure there must be a way, but if so, I don't know what it is (which
wouldn't be the first time and consider the source, I am not a big fan of
the BCB IDE).

.. Ed

Quote:
Edward Diener wrote in message
news:3f63437a (AT) newsgroups (DOT) borland.com...

Thanks, Ed. I too noticed that if I am debugging the BPL, it
will stop but not when I am debugging an EXE which loads
a BPL. I don't understand why it will not stop in the latter
case since it will stop in all other BPL code from the EXE
if I set the appropriate breakpoint in the BPL's source code.

I hope this helps but fear your project is too complex to
not have the EXE's project active.

No, I can go through the BPL's IDE and have the EXE run
as the application. That solves the problem, thanks. It does
seem that if I am debugging the EXE, it should be able to stop
anywhere in a BPL ( or DLL ) as long as the IDE finds the
equivalent .tds and source file for the latter.




Back to top
Display posts from previous:   
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> C++ Builder (IDE) All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2006 phpBB Group
SEO toolkit © 2004-2006 webmedic.