Board index » cppbuilder » _working_ solution to ignored breakpoints problem?

_working_ solution to ignored breakpoints problem?


2004-01-15 01:42:03 AM
cppbuilder61
The BCB 6.4 project lost ability to assign breakpoints - no blue dots are
shown when application starts and de{*word*81} doesn't stop on breakpoints.
I searched newsgroups for help and tried what was recommended:
- delete TDS
- delete all temporaries, precompiled headers
- rebuild all
- restart BCB (worked in the beginning, doesn't work now)
- reboot
Unforntunately neither works reliably - the breakpoints can be set sometimes
(in 5% of sessions) but it is completely unpredictable.
My question: is there some reliable way how to make debugging work at the
moment, without recreating the project completely from scratch (it is way
too big). Even reboot would be OK.
Details: project use 2 custom packages built by BCB, it contains one Pascal
unit, TDS has ~5 MB so far. CSM file has ~15 MB. Other settings are typical.
The machine has enough of RAM.
TIA,
/Pavel
 
 

Re:_working_ solution to ignored breakpoints problem?

Hi Pavel,
I experience the same thing. Do you have multiple projects in the same
project group? This seems to exacerbate the problem for me. In fact,
it seems that, for me, application projects can only be debugged if they
are the very last project in the project group.
I have a DLL project in my current project group, and one of the
application projects uses the DLL. I can reliably debug the application
project by running or making the DLL project the active one and making
the application project the host application.
I've generally found that if the last project is the active one, by
restarting BCB I can continue debugging it.
Prem.
Pavel Vozenilek wrote:
Quote
The BCB 6.4 project lost ability to assign breakpoints - no blue dots are
shown when application starts and de{*word*81} doesn't stop on breakpoints.

I searched newsgroups for help and tried what was recommended:
- delete TDS
- delete all temporaries, precompiled headers
- rebuild all
- restart BCB (worked in the beginning, doesn't work now)
- reboot

Unforntunately neither works reliably - the breakpoints can be set sometimes
(in 5% of sessions) but it is completely unpredictable.

My question: is there some reliable way how to make debugging work at the
moment, without recreating the project completely from scratch (it is way
too big). Even reboot would be OK.


Details: project use 2 custom packages built by BCB, it contains one Pascal
unit, TDS has ~5 MB so far. CSM file has ~15 MB. Other settings are typical.
The machine has enough of RAM.

TIA,
/Pavel
 

Re:_working_ solution to ignored breakpoints problem?

"Prem" < XXXX@XXXXX.COM >wrote
Quote
I experience the same thing. Do you have multiple projects in the same
project group? This seems to exacerbate the problem for me. In fact,
it seems that, for me, application projects can only be debugged if they
are the very last project in the project group.

I have a DLL project in my current project group, and one of the
application projects uses the DLL. I can reliably debug the application
project by running or making the DLL project the active one and making
the application project the host application.

I've generally found that if the last project is the active one, by
restarting BCB I can continue debugging it.

I tried and it (the last project trick) seems to work, for now.
Thanks a lot for sharing black magic art,
/Pavel
 

{smallsort}

Re:_working_ solution to ignored breakpoints problem?

"Pavel Vozenilek" < XXXX@XXXXX.COM >wrote in message news:< XXXX@XXXXX.COM >...
Quote
"Prem" < XXXX@XXXXX.COM >wrote

>I experience the same thing. Do you have multiple projects in the same
>project group? This seems to exacerbate the problem for me. In fact,
>it seems that, for me, application projects can only be debugged if they
>are the very last project in the project group.
>
>I have a DLL project in my current project group, and one of the
>application projects uses the DLL. I can reliably debug the application
>project by running or making the DLL project the active one and making
>the application project the host application.
>
>I've generally found that if the last project is the active one, by
>restarting BCB I can continue debugging it.
>
I tried and it (the last project trick) seems to work, for now.

Thanks a lot for sharing black magic art,

/Pavel
I have only one project open and still no blue dots. Nothing helps,
not even rebooting. I've had the problem very often, usually just
closing and opening the project helps, but now I'm stuck. If anybody
have any ideas, I'd appreciate.
markus