Has the OW 1.9 debugger inability to break anywhere in Windows 10 x64 been fixed ?

[Lynn McGuire]

It looks like http://www.openwatcom.org/ is dead. I cannot figure out
how to ask any questions there.

Has the OW 1.9 debugger inability to break anywhere in Windows 10 x64
been fixed ?

In other words, I set a breakpoint on a function or at a line of code
and the OW debugger goes right past the breakpoint, never stopping.

Thanks,
Lynn McGuire
***@winsim.com

[Paul S Person]

On Wed, 23 Feb 2022 14:37:56 -0600, Lynn McGuire

Post by Lynn McGuire
It looks like http://www.openwatcom.org/ is dead. I cannot figure out
how to ask any questions there.
Has the OW 1.9 debugger inability to break anywhere in Windows 10 x64
been fixed ?
In other words, I set a breakpoint on a function or at a line of code
and the OW debugger goes right past the breakpoint, never stopping.

It doesn't do that here. Never has.

Also, didn't I get an email from you some time back claiming you had
solved the problem?

[Lynn McGuire]

Post by Paul S Person
On Wed, 23 Feb 2022 14:37:56 -0600, Lynn McGuire

Post by Lynn McGuire
It looks like http://www.openwatcom.org/ is dead. I cannot figure out
how to ask any questions there.
Has the OW 1.9 debugger inability to break anywhere in Windows 10 x64
been fixed ?
In other words, I set a breakpoint on a function or at a line of code
and the OW debugger goes right past the breakpoint, never stopping.

It doesn't do that here. Never has.
Also, didn't I get an email from you some time back claiming you had
solved the problem?

No email from me on that problem that I remember.

I have huge Win32 DLLs (10 MB and 30 MB). I wonder if I am running past
some internal limit for breakpoints on Windows 10 x64 WOW.

Thanks,
Lynn

[Paul S Person]

On Thu, 24 Feb 2022 15:12:16 -0600, Lynn McGuire

Post by Lynn McGuire

Post by Paul S Person
On Wed, 23 Feb 2022 14:37:56 -0600, Lynn McGuire

Post by Lynn McGuire
It looks like http://www.openwatcom.org/ is dead. I cannot figure out
how to ask any questions there.
Has the OW 1.9 debugger inability to break anywhere in Windows 10 x64
been fixed ?
In other words, I set a breakpoint on a function or at a line of code
and the OW debugger goes right past the breakpoint, never stopping.

It doesn't do that here. Never has.
Also, didn't I get an email from you some time back claiming you had
solved the problem?

No email from me on that problem that I remember.

Then someone is using your name and, IIRC, email.

When I sent an email to someone with your name and a different email,
the response was not clear but was copied to both that Lynn McGuire's
email and, IIRC, yours.

Post by Lynn McGuire
I have huge Win32 DLLs (10 MB and 30 MB). I wonder if I am running past
some internal limit for breakpoints on Windows 10 x64 WOW.

In which case this may be a Microsoft problem.

But you presented it as an Absolute Fact Applying Everwhere. It does
/not/ apply to command-line applications.

Unfortunately, our servers are down, and have been for some time, so
there isn't much traffic here.

[Lynn McGuire]

Post by Paul S Person
On Thu, 24 Feb 2022 15:12:16 -0600, Lynn McGuire

Post by Lynn McGuire

Post by Paul S Person
On Wed, 23 Feb 2022 14:37:56 -0600, Lynn McGuire

Post by Lynn McGuire
It looks like http://www.openwatcom.org/ is dead. I cannot figure out
how to ask any questions there.
Has the OW 1.9 debugger inability to break anywhere in Windows 10 x64
been fixed ?
In other words, I set a breakpoint on a function or at a line of code
and the OW debugger goes right past the breakpoint, never stopping.

It doesn't do that here. Never has.
Also, didn't I get an email from you some time back claiming you had
solved the problem?

No email from me on that problem that I remember.

Then someone is using your name and, IIRC, email.
When I sent an email to someone with your name and a different email,
the response was not clear but was copied to both that Lynn McGuire's
email and, IIRC, yours.

Post by Lynn McGuire
I have huge Win32 DLLs (10 MB and 30 MB). I wonder if I am running past
some internal limit for breakpoints on Windows 10 x64 WOW.

In which case this may be a Microsoft problem.
But you presented it as an Absolute Fact Applying Everwhere. It does
/not/ apply to command-line applications.
Unfortunately, our servers are down, and have been for some time, so
there isn't much traffic here.

It was probably me then. I just do not remember.

My Win32 DLLs are called by both command line applications and and
Windowed applications. I usually debug via the command line application
so the windowing logic does not get in the way of the thread. So the
type of app does not matter to my problem.

I am getting very inconsistent behavior out of the watcom debugger.
Something weird is going on.

I did find a Fortran bug in my large DLL today. I fixed over 100 out of
the 200+ calls today. I will finish Monday or so.

I did build a small test Win32 app and I can debug that just fine.

Thanks,
Lynn

[Paul S Person]

On Sat, 26 Feb 2022 00:49:07 -0600, Lynn McGuire

Post by Lynn McGuire

Post by Paul S Person
On Thu, 24 Feb 2022 15:12:16 -0600, Lynn McGuire

Post by Lynn McGuire

Post by Paul S Person
On Wed, 23 Feb 2022 14:37:56 -0600, Lynn McGuire

Post by Lynn McGuire
It looks like http://www.openwatcom.org/ is dead. I cannot figure out
how to ask any questions there.
Has the OW 1.9 debugger inability to break anywhere in Windows 10 x64
been fixed ?
In other words, I set a breakpoint on a function or at a line of code
and the OW debugger goes right past the breakpoint, never stopping.

It doesn't do that here. Never has.
Also, didn't I get an email from you some time back claiming you had
solved the problem?

No email from me on that problem that I remember.

Then someone is using your name and, IIRC, email.
When I sent an email to someone with your name and a different email,
the response was not clear but was copied to both that Lynn McGuire's
email and, IIRC, yours.

Post by Lynn McGuire
I have huge Win32 DLLs (10 MB and 30 MB). I wonder if I am running past
some internal limit for breakpoints on Windows 10 x64 WOW.

In which case this may be a Microsoft problem.
But you presented it as an Absolute Fact Applying Everwhere. It does
/not/ apply to command-line applications.
Unfortunately, our servers are down, and have been for some time, so
there isn't much traffic here.

It was probably me then. I just do not remember.
My Win32 DLLs are called by both command line applications and and
Windowed applications. I usually debug via the command line application
so the windowing logic does not get in the way of the thread. So the
type of app does not matter to my problem.
I am getting very inconsistent behavior out of the watcom debugger.
Something weird is going on.
I did find a Fortran bug in my large DLL today. I fixed over 100 out of
the 200+ calls today. I will finish Monday or so.
I did build a small test Win32 app and I can debug that just fine.

If reducing the DLL size fixes the problem, then I have no idea what
to say.

Except that, since 1.9 is /entirely/ 32-bit, at least the debugger can
run the target directly.

The debugger can /appear/ to do this, of course, if the executable and
the source are not in synch with each other. It doesn't actually debug
the source code; it debugs the binary and uses the source for
illustration. The debugging info links the two.

But that is usually quite visible in wdw: the allowed break points
simply don't line up with the source shown. The only solution is to
recompile the current source so the break points do line up properly.

[Lynn McGuire]

Post by Paul S Person
On Sat, 26 Feb 2022 00:49:07 -0600, Lynn McGuire

Post by Lynn McGuire

Post by Paul S Person
On Thu, 24 Feb 2022 15:12:16 -0600, Lynn McGuire

Post by Lynn McGuire

Post by Paul S Person
On Wed, 23 Feb 2022 14:37:56 -0600, Lynn McGuire

Post by Lynn McGuire
It looks like http://www.openwatcom.org/ is dead. I cannot figure out
how to ask any questions there.
Has the OW 1.9 debugger inability to break anywhere in Windows 10 x64
been fixed ?
In other words, I set a breakpoint on a function or at a line of code
and the OW debugger goes right past the breakpoint, never stopping.

It doesn't do that here. Never has.
Also, didn't I get an email from you some time back claiming you had
solved the problem?

No email from me on that problem that I remember.

Then someone is using your name and, IIRC, email.
When I sent an email to someone with your name and a different email,
the response was not clear but was copied to both that Lynn McGuire's
email and, IIRC, yours.

Post by Lynn McGuire
I have huge Win32 DLLs (10 MB and 30 MB). I wonder if I am running past
some internal limit for breakpoints on Windows 10 x64 WOW.

In which case this may be a Microsoft problem.
But you presented it as an Absolute Fact Applying Everwhere. It does
/not/ apply to command-line applications.
Unfortunately, our servers are down, and have been for some time, so
there isn't much traffic here.

It was probably me then. I just do not remember.
My Win32 DLLs are called by both command line applications and and
Windowed applications. I usually debug via the command line application
so the windowing logic does not get in the way of the thread. So the
type of app does not matter to my problem.
I am getting very inconsistent behavior out of the watcom debugger.
Something weird is going on.
I did find a Fortran bug in my large DLL today. I fixed over 100 out of
the 200+ calls today. I will finish Monday or so.
I did build a small test Win32 app and I can debug that just fine.

If reducing the DLL size fixes the problem, then I have no idea what
to say.
Except that, since 1.9 is /entirely/ 32-bit, at least the debugger can
run the target directly.
The debugger can /appear/ to do this, of course, if the executable and
the source are not in synch with each other. It doesn't actually debug
the source code; it debugs the binary and uses the source for
illustration. The debugging info links the two.
But that is usually quite visible in wdw: the allowed break points
simply don't line up with the source shown. The only solution is to
recompile the current source so the break points do line up properly.

I only tested with a Win32 EXE in WDW. I did not put a Win32 DLL in it
though. That is the next test.

Lynn

[Lynn McGuire]

Post by Paul S Person
On Sat, 26 Feb 2022 00:49:07 -0600, Lynn McGuire

Post by Paul S Person
On Thu, 24 Feb 2022 15:12:16 -0600, Lynn McGuire

Post by Lynn McGuire

Post by Paul S Person
On Wed, 23 Feb 2022 14:37:56 -0600, Lynn McGuire

Post by Lynn McGuire
It looks like http://www.openwatcom.org/ is dead. I cannot figure out
how to ask any questions there.
Has the OW 1.9 debugger inability to break anywhere in Windows 10 x64
been fixed ?
In other words, I set a breakpoint on a function or at a line of code
and the OW debugger goes right past the breakpoint, never stopping.

It doesn't do that here. Never has.
Also, didn't I get an email from you some time back claiming you had
solved the problem?

No email from me on that problem that I remember.

Then someone is using your name and, IIRC, email.
When I sent an email to someone with your name and a different email,
the response was not clear but was copied to both that Lynn McGuire's
email and, IIRC, yours.

Post by Lynn McGuire
I have huge Win32 DLLs (10 MB and 30 MB).  I wonder if I am running
past
some internal limit for breakpoints on Windows 10 x64 WOW.

In which case this may be a Microsoft problem.
But you presented it as an Absolute Fact Applying Everwhere. It does
/not/ apply to command-line applications.
Unfortunately, our servers are down, and have been for some time, so
there isn't much traffic here.

It was probably me then.  I just do not remember.
My Win32 DLLs are called by both command line applications and and
Windowed applications.  I usually debug via the command line application
so the windowing logic does not get in the way of the thread.  So the
type of app does not matter to my problem.
I am getting very inconsistent behavior out of the watcom debugger.
Something weird is going on.
I did find a Fortran bug in my large DLL today.  I fixed over 100 out of
the 200+ calls today.  I will finish Monday or so.
I did build a small test Win32 app and I can debug that just fine.

If reducing the DLL size fixes the problem, then I have no idea what
to say.
Except that, since 1.9 is /entirely/ 32-bit, at least the debugger can
run the target directly.
The debugger can /appear/ to do this, of course, if the executable and
the source are not in synch with each other. It doesn't actually debug
the source code; it debugs the binary and uses the source for
illustration. The debugging info links the two.
But that is usually quite visible in wdw: the allowed break points
simply don't line up with the source shown. The only solution is to
recompile the current source so the break points do line up properly.

I only tested with a Win32 EXE in WDW.  I did not put a Win32 DLL in it
though.  That is the next test.
Lynn

And I just confirmed that my Fortran code problem did not affect the
debugger breakpoints. The debugger breakpoints still do not work for me
now that I fixed all those.

I am talking to Jiri Malek and Michal Necasek on other channels. They
are not seeing the problem either but neither use Win32 DLLs also.

I still need to built a test Win32 DLL to see if I can duplicate the
problem in some non-related code that I can share.

Lynn

[Lynn McGuire]

Post by Lynn McGuire
It looks like http://www.openwatcom.org/ is dead. I cannot figure out
how to ask any questions there.
Has the OW 1.9 debugger inability to break anywhere in Windows 10 x64
been fixed ?
In other words, I set a breakpoint on a function or at a line of code
and the OW debugger goes right past the breakpoint, never stopping.
Thanks,
Lynn McGuire

BTW, if I a use a small win32 executable then the debugger break points
work just fine. So the problem is either that all of the breakpoints
are in my DLLs or that my Win32 DLLs are so large (10 MB and 30 MB).

These breakpoints work just fine on my Windows 7 x64 PC.

Lynn