# Catalyst2 break point
**URL:** https://discourse.paraview.org/t/catalyst2-break-point/13156
**Category:** ParaView Support
**Created:** [November 1, 2023, 5:19pm UTC](https://discourse.paraview.org/t/catalyst2-break-point/13156 "2023-11-01T17:19:11Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@m.novak](https://discourse.paraview.org/u/m.novak)
#### Post date: [November 1, 2023, 5:19pm UTC](https://discourse.paraview.org/t/catalyst2-break-point/13156/1 "2023-11-01T17:19:11Z")
Dear support.
I implemented catalystV2 adaptor for our code base.
It functions well, the only thing I noticed is that the breakpoints does not work. Only pause and continue.
I set root/catalyst/state/time as double. The
PARAVIEW\_LOG\_CATALYST\_VERBOSITY=INFO
shows it got received.
```auto
( 2.149s) [pvbatch]vtkCPPythonScriptV2Help:675 INFO| . . } 0.000 s: DoLive
( 2.149s) [pvbatch] ParaViewCatalyst.cxx:384 INFO| . } 0.945 s: co-processing for timestep=1, time=0.000001
```
If I set in paraview I set catalyst connect, then breakpoint-\>time-\>0.000001 and set.
the breakpoint does not pause the simulation.
in the terminal I launched client paraview, empty lines starts to appear each time-step.
```auto
( 9.809s) [paraview] vtkLiveInsituLink.cxx:409 INFO| Listening for primary Catalyst connection on `login:22222`
Accepting connection(s): login:22222
```
Pausing the simulation and setting the breakpoint for a later time (0.00005) and then continue also does not pause the simulation.
* * *
Paraview version 5.11.0
Linux login 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86\_64 x86\_64 x86\_64 GNU/Linux
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [November 1, 2023, 6:34pm UTC](https://discourse.paraview.org/t/catalyst2-break-point/13156/2 "2023-11-01T18:34:36Z")
Where did you set a breakpoint? What debugger are you using?
---
### Author:  [@Christos\_Tsolakis](https://discourse.paraview.org/u/Christos_Tsolakis)
#### Post date: [November 1, 2023, 11:18pm UTC](https://discourse.paraview.org/t/catalyst2-break-point/13156/3 "2023-11-01T23:18:30Z")
They refer to catalyst breakpoints that can be set from the ParaView UI which are known to have issues. See [https://gitlab.kitware.com/paraview/paraview/-/issues/21735](https://gitlab.kitware.com/paraview/paraview/-/issues/21735)
---
### Author:  [@m.novak](https://discourse.paraview.org/u/m.novak)
#### Post date: [November 6, 2023, 8:22am UTC](https://discourse.paraview.org/t/catalyst2-break-point/13156/4 "2023-11-06T08:22:38Z")
Yes, is there a plan to tackle this? It’s an important feature for catalyst.
---
### Author:  [@Lucas\_Givord](https://discourse.paraview.org/u/Lucas_Givord)
#### Post date: [November 6, 2023, 3:11pm UTC](https://discourse.paraview.org/t/catalyst2-break-point/13156/5 "2023-11-06T15:11:37Z")
it’s not planned for the moment AFAIK
FYI @nicolas.vuaille @Francois_Mazen
---
### Author:  [@Francois\_Mazen](https://discourse.paraview.org/u/Francois_Mazen)
#### Post date: [November 6, 2023, 5:47pm UTC](https://discourse.paraview.org/t/catalyst2-break-point/13156/6 "2023-11-06T17:47:37Z")
> [@m.novak](#):
>
> Yes, is there a plan to tackle this? It’s an important feature for catalyst.
If this is a showstopper, you should contact Kitware to get this fixed though advanced support: [https://www.kitware.com/contact/](https://www.kitware.com/contact/)
---
### Author:  [@m.novak](https://discourse.paraview.org/u/m.novak)
#### Post date: [November 28, 2023, 9:01am UTC](https://discourse.paraview.org/t/catalyst2-break-point/13156/7 "2023-11-28T09:01:19Z")
It is not a showstopper, it’s just a pity that this issue, although known, has not been resolved yet.