Debugger set breakpoint with full filename

[Bill Medland]

I've spent time looking for the answer and trying the (to me) obvious
options and now I give in.

How, in the debugger, do I specify "Set a break point at DllMain of
E:\BIN.50A..MYDLL.DLL"
without the debugger complaining about syntax etc.?

If someone answers then I am prepared to add the info to debugger.sgml

Bill

[Bill Medland]

"Bill Medland"  wrote in message
news:[e-mail]...
> I've spent time looking for the answer and trying the (to me) obvious
> options and now I give in.
>
> How, in the debugger, do I specify "Set a break point at DllMain of
> E:\BIN.50A..MYDLL.DLL"
> without the debugger complaining about syntax etc.?
>
> If someone answers then I am prepared to add the info to debugger.sgml
>
> Bill

OK.  To break at function foo of dll E:\somepath\MyDll.DLL

break MYDLL.DLL.foo

I'll update the file.

NOW the real question.

I am chasing a bug which makes no sense.  I want to single-step through the
DLL's DllMain but since it isn't exported the debugger can't get its address
(I presume) so I can't set it as a break point.
Is there a way to figure out what it's address is?

Bill

[eric]

> break MYDLL.DLL.foo

you can eventually omit the .DLL too (except for DLL which don't
have the DLL extension, like drv, acm...)
A+

[eric]

Bill Medland a écrit :
> I've spent time looking for the answer and trying the (to me) obvious
> options and now I give in.
>
> How, in the debugger, do I specify "Set a break point at DllMain of
> E:\BIN.50A..MYDLL.DLL"
> without the debugger complaining about syntax etc.?

hmmm debugger isn't ready to handle DLL names which contain '.'

another solution is to ask the debugger to break on each DLL loading.
set $BreakOnDllLoad = 1
then, you would be able to add a breakpoint on DllMain (which, I assume
would be exported from the DLL, meaning its symbol will be known to the
debugger)

A+