Application hangs with breakpoint

[=?Utf-8?B?THVib21pcg==?=]

Hi,

When I use a break point and and than hit F5, my applicaiton continues and
shows a dialog. When I hit a button in the dialog, my application will hang,
inclusive Visual studio, and dialog will be left on the screen (execution
will not go into a button-click handler).

If I don't use a break point, everything works fine.

Envirnoment:
OS is Vista 64,
application is 32,
database Sql Express
MS VS Professional

Any idea? It seems like something could be wrong with memory...
Thanks,

Lubomir

[christery]

On 9 Feb, 01:27, Lubomir <[e-mail]:

Hi,

When I use a break point and and than hit F5, my applicaiton continues and
shows a dialog. When I hit a button in the dialog, my application will hang,
inclusive Visual studio, and dialog will be left on the screen (execution
will not go into a button-click handler).

If I don't use a break point, everything works fine.

Envirnoment:
OS is Vista 64,
application is 32,
database Sql Express
MS VS Professional

Any idea? It seems like something could be wrong with memory...
Thanks,

Lubomir

try stepping into code and run to cursor to get around the problem
never seen vista/vs p app, but it should not be a mem problem (HW)
that only targets breakpoints... sounds like vs p is damaged in the
debug mode someway
//CY

[=?Utf-8?B?THVib21pcg==?=]

"ch*******@gmail.com" wrote:

On 9 Feb, 01:27, Lubomir <[e-mail]:

Hi,

When I use a break point and and than hit F5, my applicaiton continues and
shows a dialog. When I hit a button in the dialog, my application will hang,
inclusive Visual studio, and dialog will be left on the screen (execution
will not go into a button-click handler).

If I don't use a break point, everything works fine.

Envirnoment:
OS is Vista 64,
application is 32,
database Sql Express
MS VS Professional

Any idea? It seems like something could be wrong with memory...
Thanks,

Lubomir

try stepping into code and run to cursor to get around the problem
never seen vista/vs p app, but it should not be a mem problem (HW)
that only targets breakpoints... sounds like vs p is damaged in the
debug mode someway
//CY

I found out that it is related to the 64 bit remote debugger that is invoked
behind the scene bt VS. When I replaced the 64 bits dll with 32, everything
works fine.

Is there any way how to set up from VS IDE that while debugging, the VS
should use 32 bits dll for remote debugger instead of 64? Al my app is set up
for 32 bits OS target - despite them VS is using 64 bits remote debugger for
accessig SQL Express.

Lubomir

[christery]

On 11 Feb, 18:45, Lubomir <[e-mail]:

"[e-mail]" wrote:

On 9 Feb, 01:27, Lubomir <[e-mail]:

Hi,

When I use a break point and and than hit F5, my applicaiton continuesand
shows a dialog. When I hit a button in the dialog, my application willhang,
inclusive Visual studio, and dialog will be left on the screen (execution
will not go into a button-click handler).

If I don't use a break point, everything works fine.

Envirnoment:
OS is Vista 64,
application is 32,
database Sql Express
MS VS Professional

Any idea? It seems like something could be wrong with memory...
Thanks,

Lubomir

try stepping into code and run to cursor to get around the problem
never seen vista/vs p app, but it should not be a mem problem (HW)
that only targets breakpoints... sounds like vs p is damaged in the
debug mode someway
//CY

I found out that it is related to the 64 bit remote debugger that is invoked
behind the scene bt VS. When I replaced the 64 bits dll with 32, everything
works fine.

Is there any way how to set up from VS IDE that while debugging, the VS
should use 32 bits dll for remote debugger instead of 64? Al my app is setup
for 32 bits OS target - despite them VS is using 64 bits remote debugger for
accessig SQL Express.

Lubomir- Dölj citerad text -

- Visa citerad text -

WMware or virtual pc comes to mind, if its a bug in VS then trying to
fix it might just be a waste of time, myself just playing with itanium
IA64 and there you should not try pressing 32 bit code as the
instructions has changed a bit (Also running OpenVMS as OS so its a
bit off), so u are probably running x64, amd:s invention and it will
probably comply to 32bit code but u cant use the adressrange if im
correctly informed.

building for 32 bit, use 32 bit iron.. simple.. get a kvm and stack up
some hardwae under the desk, that always makes the office cleaning
persons happy, lots of cables to get intangled to ;)

Got a W95 (virtual pc, needed for some aincent programs), xp on WM in
a blade somewhere up in the computer room (nice to snapshot and
rollback), NT4 running a couple of VAX emulators, pdp (charon), 2 XP
one in our AD (cant do anything more tha check mail with that) and
anoter in our old domain where im domainadmin and can do whatever...
servers are just some alpha ds20/25 and an I64 just to play with for
now....

I dont think 1 machine will be just the right tool for everything...

Just a suggestion....

nowdays most of the homecomputers have more memory on the grafics than
I use on my VMS servers... a strange strange world...

//CY