Hello developers,
setting a breakpoint with Ctrl_F5 doesn't invoke the debugger.
Regards,
Stephan
In order for this site to work correctly we need to store a small file (called a cookie) on your computer. Most every site in the world does this, however since the 25th of May 2011, by law we have to get your permission first. Please abandon the forum if you disagree.
Para que este foro funcione correctamente es necesario guardar un pequeño fichero (llamado cookie) en su ordenador. La mayoría de los sitios de Internet lo hacen, no obstante desde el 25 de Marzo de 2011 y por ley, necesitamos de su permiso con antelación. Abandone este foro si no está conforme.
Para que este foro funcione correctamente es necesario guardar un pequeño fichero (llamado cookie) en su ordenador. La mayoría de los sitios de Internet lo hacen, no obstante desde el 25 de Marzo de 2011 y por ley, necesitamos de su permiso con antelación. Abandone este foro si no está conforme.
Breakpoint
-
Stephan Hennekens
- Mensajes: 305
- Registrado: Jue Nov 30, 2006 12:17 am
-
Nick Hilder
- Mensajes: 328
- Registrado: Mar Nov 21, 2006 2:10 am
Breakpoint
Hi Stephan
It does for me, that said though, I find the whole breakpoint thing to be a
little hit and miss.
If breakpoint fails to invoke the debugger I usually just make a tiny change
to the prg file the break point is in, which forces it to be rebuilt, which
in turn forces the breakpoint to be redone I guess, and that seems to be my
work around. It's especially flaky if you have a break point in one prg that
you are using and then switch to another prg and put one it without making a
change to that prg. It is hit and miss, it does work a lot of the time.
Something is getting confussed somewhere
Over all I have got used to this and can get it working pretty much every
time now, I have been working in a big app for the last 2 months(big for me)
it has about 18 classes/prg files and I can get the debugger working
whenever i need it. I use it a lot.
Cheers
Nick
"Stephan Hennekens" <stephan.hennekens@wur.nl> wrote in message
news:[email=48582a49@ozsrv2.ozlan.local...]48582a49@ozsrv2.ozlan.local...[/email]
> Hello developers,
>
> setting a breakpoint with Ctrl_F5 doesn't invoke the debugger.
>
> Regards,
> Stephan
>
It does for me, that said though, I find the whole breakpoint thing to be a
little hit and miss.
If breakpoint fails to invoke the debugger I usually just make a tiny change
to the prg file the break point is in, which forces it to be rebuilt, which
in turn forces the breakpoint to be redone I guess, and that seems to be my
work around. It's especially flaky if you have a break point in one prg that
you are using and then switch to another prg and put one it without making a
change to that prg. It is hit and miss, it does work a lot of the time.
Something is getting confussed somewhere
Over all I have got used to this and can get it working pretty much every
time now, I have been working in a big app for the last 2 months(big for me)
it has about 18 classes/prg files and I can get the debugger working
whenever i need it. I use it a lot.
Cheers
Nick
"Stephan Hennekens" <stephan.hennekens@wur.nl> wrote in message
news:[email=48582a49@ozsrv2.ozlan.local...]48582a49@ozsrv2.ozlan.local...[/email]
> Hello developers,
>
> setting a breakpoint with Ctrl_F5 doesn't invoke the debugger.
>
> Regards,
> Stephan
>
-
Nick Hilder
- Mensajes: 328
- Registrado: Mar Nov 21, 2006 2:10 am
Breakpoint
Hi Stephan
It does for me, that said though, I find the whole breakpoint thing to be a
little hit and miss.
If breakpoint fails to invoke the debugger I usually just make a tiny change
to the prg file the break point is in, which forces it to be rebuilt, which
in turn forces the breakpoint to be redone I guess, and that seems to be my
work around. It's especially flaky if you have a break point in one prg that
you are using and then switch to another prg and put one it without making a
change to that prg. It is hit and miss, it does work a lot of the time.
Something is getting confussed somewhere
Over all I have got used to this and can get it working pretty much every
time now, I have been working in a big app for the last 2 months(big for me)
it has about 18 classes/prg files and I can get the debugger working
whenever i need it. I use it a lot.
Cheers
Nick
"Stephan Hennekens" <stephan.hennekens@wur.nl> wrote in message
news:[email=48582a49@ozsrv2.ozlan.local...]48582a49@ozsrv2.ozlan.local...[/email]
> Hello developers,
>
> setting a breakpoint with Ctrl_F5 doesn't invoke the debugger.
>
> Regards,
> Stephan
>
It does for me, that said though, I find the whole breakpoint thing to be a
little hit and miss.
If breakpoint fails to invoke the debugger I usually just make a tiny change
to the prg file the break point is in, which forces it to be rebuilt, which
in turn forces the breakpoint to be redone I guess, and that seems to be my
work around. It's especially flaky if you have a break point in one prg that
you are using and then switch to another prg and put one it without making a
change to that prg. It is hit and miss, it does work a lot of the time.
Something is getting confussed somewhere
Over all I have got used to this and can get it working pretty much every
time now, I have been working in a big app for the last 2 months(big for me)
it has about 18 classes/prg files and I can get the debugger working
whenever i need it. I use it a lot.
Cheers
Nick
"Stephan Hennekens" <stephan.hennekens@wur.nl> wrote in message
news:[email=48582a49@ozsrv2.ozlan.local...]48582a49@ozsrv2.ozlan.local...[/email]
> Hello developers,
>
> setting a breakpoint with Ctrl_F5 doesn't invoke the debugger.
>
> Regards,
> Stephan
>
Breakpoint
Stephan,
> setting a breakpoint with Ctrl_F5 doesn't invoke the debugger.
Make sure that "Include debug info" is checked in the "Project properties"
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
> setting a breakpoint with Ctrl_F5 doesn't invoke the debugger.
Make sure that "Include debug info" is checked in the "Project properties"
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
Breakpoint
Stephan,
> setting a breakpoint with Ctrl_F5 doesn't invoke the debugger.
Make sure that "Include debug info" is checked in the "Project properties"
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
> setting a breakpoint with Ctrl_F5 doesn't invoke the debugger.
Make sure that "Include debug info" is checked in the "Project properties"
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
Breakpoint
Nick,
in previous versions of Xailer, when "Include debug info" was setted, you
have to rebuild the entire project in order to recompile all modules with
that debug info. Later, when releasing the program to production, it was
needed to clear that option and rebuild the entire project again to drop the
debug info.
But since version 1.8, it's Xailer itself which manages the situation,
recompiling each module (with or without debug info) only if needed.
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
in previous versions of Xailer, when "Include debug info" was setted, you
have to rebuild the entire project in order to recompile all modules with
that debug info. Later, when releasing the program to production, it was
needed to clear that option and rebuild the entire project again to drop the
debug info.
But since version 1.8, it's Xailer itself which manages the situation,
recompiling each module (with or without debug info) only if needed.
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
Breakpoint
Nick,
in previous versions of Xailer, when "Include debug info" was setted, you
have to rebuild the entire project in order to recompile all modules with
that debug info. Later, when releasing the program to production, it was
needed to clear that option and rebuild the entire project again to drop the
debug info.
But since version 1.8, it's Xailer itself which manages the situation,
recompiling each module (with or without debug info) only if needed.
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
in previous versions of Xailer, when "Include debug info" was setted, you
have to rebuild the entire project in order to recompile all modules with
that debug info. Later, when releasing the program to production, it was
needed to clear that option and rebuild the entire project again to drop the
debug info.
But since version 1.8, it's Xailer itself which manages the situation,
recompiling each module (with or without debug info) only if needed.
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
-
Stephan Hennekens
- Mensajes: 305
- Registrado: Jue Nov 30, 2006 12:17 am
Breakpoint
Jose,
Thanks for your response.
I always 'Debug info' on. Anyway, it works now, but have no idea why it
didn;t work before.
Regards,
Stephan
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:[email=4858ca77@ozsrv2.ozlan.local...]4858ca77@ozsrv2.ozlan.local...[/email]
> Stephan,
>
>> setting a breakpoint with Ctrl_F5 doesn't invoke the debugger.
>
> Make sure that "Include debug info" is checked in the "Project properties"
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info
>
Thanks for your response.
I always 'Debug info' on. Anyway, it works now, but have no idea why it
didn;t work before.
Regards,
Stephan
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:[email=4858ca77@ozsrv2.ozlan.local...]4858ca77@ozsrv2.ozlan.local...[/email]
> Stephan,
>
>> setting a breakpoint with Ctrl_F5 doesn't invoke the debugger.
>
> Make sure that "Include debug info" is checked in the "Project properties"
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info
>
-
Stephan Hennekens
- Mensajes: 305
- Registrado: Jue Nov 30, 2006 12:17 am
Breakpoint
Jose,
Thanks for your response.
I always 'Debug info' on. Anyway, it works now, but have no idea why it
didn;t work before.
Regards,
Stephan
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:[email=4858ca77@ozsrv2.ozlan.local...]4858ca77@ozsrv2.ozlan.local...[/email]
> Stephan,
>
>> setting a breakpoint with Ctrl_F5 doesn't invoke the debugger.
>
> Make sure that "Include debug info" is checked in the "Project properties"
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info
>
Thanks for your response.
I always 'Debug info' on. Anyway, it works now, but have no idea why it
didn;t work before.
Regards,
Stephan
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:[email=4858ca77@ozsrv2.ozlan.local...]4858ca77@ozsrv2.ozlan.local...[/email]
> Stephan,
>
>> setting a breakpoint with Ctrl_F5 doesn't invoke the debugger.
>
> Make sure that "Include debug info" is checked in the "Project properties"
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info
>
-
Stephan Hennekens
- Mensajes: 305
- Registrado: Jue Nov 30, 2006 12:17 am
Breakpoint
Thanks Nick.
Regards,
Stephan
"Nick Hilder" <nick_n0_spam_atcapsol.com.au> wrote in message
news:[email=48584e5c@ozsrv2.ozlan.local...]48584e5c@ozsrv2.ozlan.local...[/email]
> Hi Stephan
>
> It does for me, that said though, I find the whole breakpoint thing to be
> a little hit and miss.
>
> If breakpoint fails to invoke the debugger I usually just make a tiny
> change to the prg file the break point is in, which forces it to be
> rebuilt, which in turn forces the breakpoint to be redone I guess, and
> that seems to be my work around. It's especially flaky if you have a break
> point in one prg that you are using and then switch to another prg and put
> one it without making a change to that prg. It is hit and miss, it does
> work a lot of the time. Something is getting confussed somewhere
>
> Over all I have got used to this and can get it working pretty much every
> time now, I have been working in a big app for the last 2 months(big for
> me) it has about 18 classes/prg files and I can get the debugger working
> whenever i need it. I use it a lot.
>
> Cheers
>
> Nick
>
>
>
>
> "Stephan Hennekens" <stephan.hennekens@wur.nl> wrote in message
> news:[email=48582a49@ozsrv2.ozlan.local...]48582a49@ozsrv2.ozlan.local...[/email]
>> Hello developers,
>>
>> setting a breakpoint with Ctrl_F5 doesn't invoke the debugger.
>>
>> Regards,
>> Stephan
>>
>
>
Regards,
Stephan
"Nick Hilder" <nick_n0_spam_atcapsol.com.au> wrote in message
news:[email=48584e5c@ozsrv2.ozlan.local...]48584e5c@ozsrv2.ozlan.local...[/email]
> Hi Stephan
>
> It does for me, that said though, I find the whole breakpoint thing to be
> a little hit and miss.
>
> If breakpoint fails to invoke the debugger I usually just make a tiny
> change to the prg file the break point is in, which forces it to be
> rebuilt, which in turn forces the breakpoint to be redone I guess, and
> that seems to be my work around. It's especially flaky if you have a break
> point in one prg that you are using and then switch to another prg and put
> one it without making a change to that prg. It is hit and miss, it does
> work a lot of the time. Something is getting confussed somewhere
>
> Over all I have got used to this and can get it working pretty much every
> time now, I have been working in a big app for the last 2 months(big for
> me) it has about 18 classes/prg files and I can get the debugger working
> whenever i need it. I use it a lot.
>
> Cheers
>
> Nick
>
>
>
>
> "Stephan Hennekens" <stephan.hennekens@wur.nl> wrote in message
> news:[email=48582a49@ozsrv2.ozlan.local...]48582a49@ozsrv2.ozlan.local...[/email]
>> Hello developers,
>>
>> setting a breakpoint with Ctrl_F5 doesn't invoke the debugger.
>>
>> Regards,
>> Stephan
>>
>
>
-
Stephan Hennekens
- Mensajes: 305
- Registrado: Jue Nov 30, 2006 12:17 am
Breakpoint
Thanks Nick.
Regards,
Stephan
"Nick Hilder" <nick_n0_spam_atcapsol.com.au> wrote in message
news:[email=48584e5c@ozsrv2.ozlan.local...]48584e5c@ozsrv2.ozlan.local...[/email]
> Hi Stephan
>
> It does for me, that said though, I find the whole breakpoint thing to be
> a little hit and miss.
>
> If breakpoint fails to invoke the debugger I usually just make a tiny
> change to the prg file the break point is in, which forces it to be
> rebuilt, which in turn forces the breakpoint to be redone I guess, and
> that seems to be my work around. It's especially flaky if you have a break
> point in one prg that you are using and then switch to another prg and put
> one it without making a change to that prg. It is hit and miss, it does
> work a lot of the time. Something is getting confussed somewhere
>
> Over all I have got used to this and can get it working pretty much every
> time now, I have been working in a big app for the last 2 months(big for
> me) it has about 18 classes/prg files and I can get the debugger working
> whenever i need it. I use it a lot.
>
> Cheers
>
> Nick
>
>
>
>
> "Stephan Hennekens" <stephan.hennekens@wur.nl> wrote in message
> news:[email=48582a49@ozsrv2.ozlan.local...]48582a49@ozsrv2.ozlan.local...[/email]
>> Hello developers,
>>
>> setting a breakpoint with Ctrl_F5 doesn't invoke the debugger.
>>
>> Regards,
>> Stephan
>>
>
>
Regards,
Stephan
"Nick Hilder" <nick_n0_spam_atcapsol.com.au> wrote in message
news:[email=48584e5c@ozsrv2.ozlan.local...]48584e5c@ozsrv2.ozlan.local...[/email]
> Hi Stephan
>
> It does for me, that said though, I find the whole breakpoint thing to be
> a little hit and miss.
>
> If breakpoint fails to invoke the debugger I usually just make a tiny
> change to the prg file the break point is in, which forces it to be
> rebuilt, which in turn forces the breakpoint to be redone I guess, and
> that seems to be my work around. It's especially flaky if you have a break
> point in one prg that you are using and then switch to another prg and put
> one it without making a change to that prg. It is hit and miss, it does
> work a lot of the time. Something is getting confussed somewhere
>
> Over all I have got used to this and can get it working pretty much every
> time now, I have been working in a big app for the last 2 months(big for
> me) it has about 18 classes/prg files and I can get the debugger working
> whenever i need it. I use it a lot.
>
> Cheers
>
> Nick
>
>
>
>
> "Stephan Hennekens" <stephan.hennekens@wur.nl> wrote in message
> news:[email=48582a49@ozsrv2.ozlan.local...]48582a49@ozsrv2.ozlan.local...[/email]
>> Hello developers,
>>
>> setting a breakpoint with Ctrl_F5 doesn't invoke the debugger.
>>
>> Regards,
>> Stephan
>>
>
>
-
Nick Hilder
- Mensajes: 328
- Registrado: Mar Nov 21, 2006 2:10 am
Breakpoint
Thats pretty much it, sometime it just doesn't work and I don't know why
either
Jose, how are break points stored? If I know that, next time it happens I
can have a look and see if they are correct
Nick
"Stephan Hennekens" <stephan.hennekens@wur.nl> wrote in message
news:[email=48598bac@ozsrv2.ozlan.local...]48598bac@ozsrv2.ozlan.local...[/email]
> Jose,
> Thanks for your response.
> I always 'Debug info' on. Anyway, it works now, but have no idea why it
> didn;t work before.
> Regards,
> Stephan
>
> "Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
> news:[email=4858ca77@ozsrv2.ozlan.local...]4858ca77@ozsrv2.ozlan.local...[/email]
>> Stephan,
>>
>>> setting a breakpoint with Ctrl_F5 doesn't invoke the debugger.
>>
>> Make sure that "Include debug info" is checked in the "Project
>> properties"
>>
>> --
>> Regards,
>>
>> Jose F. Gimenez
>> http://www.xailer.com
>> http://www.xailer.info
>>
>
>
either
Jose, how are break points stored? If I know that, next time it happens I
can have a look and see if they are correct
Nick
"Stephan Hennekens" <stephan.hennekens@wur.nl> wrote in message
news:[email=48598bac@ozsrv2.ozlan.local...]48598bac@ozsrv2.ozlan.local...[/email]
> Jose,
> Thanks for your response.
> I always 'Debug info' on. Anyway, it works now, but have no idea why it
> didn;t work before.
> Regards,
> Stephan
>
> "Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
> news:[email=4858ca77@ozsrv2.ozlan.local...]4858ca77@ozsrv2.ozlan.local...[/email]
>> Stephan,
>>
>>> setting a breakpoint with Ctrl_F5 doesn't invoke the debugger.
>>
>> Make sure that "Include debug info" is checked in the "Project
>> properties"
>>
>> --
>> Regards,
>>
>> Jose F. Gimenez
>> http://www.xailer.com
>> http://www.xailer.info
>>
>
>
-
Nick Hilder
- Mensajes: 328
- Registrado: Mar Nov 21, 2006 2:10 am
Breakpoint
Thats pretty much it, sometime it just doesn't work and I don't know why
either
Jose, how are break points stored? If I know that, next time it happens I
can have a look and see if they are correct
Nick
"Stephan Hennekens" <stephan.hennekens@wur.nl> wrote in message
news:[email=48598bac@ozsrv2.ozlan.local...]48598bac@ozsrv2.ozlan.local...[/email]
> Jose,
> Thanks for your response.
> I always 'Debug info' on. Anyway, it works now, but have no idea why it
> didn;t work before.
> Regards,
> Stephan
>
> "Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
> news:[email=4858ca77@ozsrv2.ozlan.local...]4858ca77@ozsrv2.ozlan.local...[/email]
>> Stephan,
>>
>>> setting a breakpoint with Ctrl_F5 doesn't invoke the debugger.
>>
>> Make sure that "Include debug info" is checked in the "Project
>> properties"
>>
>> --
>> Regards,
>>
>> Jose F. Gimenez
>> http://www.xailer.com
>> http://www.xailer.info
>>
>
>
either
Jose, how are break points stored? If I know that, next time it happens I
can have a look and see if they are correct
Nick
"Stephan Hennekens" <stephan.hennekens@wur.nl> wrote in message
news:[email=48598bac@ozsrv2.ozlan.local...]48598bac@ozsrv2.ozlan.local...[/email]
> Jose,
> Thanks for your response.
> I always 'Debug info' on. Anyway, it works now, but have no idea why it
> didn;t work before.
> Regards,
> Stephan
>
> "Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
> news:[email=4858ca77@ozsrv2.ozlan.local...]4858ca77@ozsrv2.ozlan.local...[/email]
>> Stephan,
>>
>>> setting a breakpoint with Ctrl_F5 doesn't invoke the debugger.
>>
>> Make sure that "Include debug info" is checked in the "Project
>> properties"
>>
>> --
>> Regards,
>>
>> Jose F. Gimenez
>> http://www.xailer.com
>> http://www.xailer.info
>>
>
>
Breakpoint
Stephan,
> I always 'Debug info' on. Anyway, it works now, but have no idea why it
> didn;t work before.
Then, probably that .obj was not recompiled with last Xailer version.
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
> I always 'Debug info' on. Anyway, it works now, but have no idea why it
> didn;t work before.
Then, probably that .obj was not recompiled with last Xailer version.
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
Breakpoint
Stephan,
> I always 'Debug info' on. Anyway, it works now, but have no idea why it
> didn;t work before.
Then, probably that .obj was not recompiled with last Xailer version.
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
> I always 'Debug info' on. Anyway, it works now, but have no idea why it
> didn;t work before.
Then, probably that .obj was not recompiled with last Xailer version.
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
Breakpoint
Nick,
> Thats pretty much it, sometime it just doesn't work and I don't know why
> either
>
> Jose, how are break points stored? If I know that, next time it happens I
> can have a look and see if they are correct
I'm affraid it's not so easy. The BP are shown in red marked lines in the
code editor, and are passed from the IDE to the program at program's
startup.
In either case, check that the BP is setted in a correct line. I.e. if you
have a sentence, broken in several source lines, then only the last line is
BP suitable. There are also other cases where BP won't work; i.e. lines with
ENDIF, ENDDO, END OBJECT, etc.
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
> Thats pretty much it, sometime it just doesn't work and I don't know why
> either
>
> Jose, how are break points stored? If I know that, next time it happens I
> can have a look and see if they are correct
I'm affraid it's not so easy. The BP are shown in red marked lines in the
code editor, and are passed from the IDE to the program at program's
startup.
In either case, check that the BP is setted in a correct line. I.e. if you
have a sentence, broken in several source lines, then only the last line is
BP suitable. There are also other cases where BP won't work; i.e. lines with
ENDIF, ENDDO, END OBJECT, etc.
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
Breakpoint
Nick,
> Thats pretty much it, sometime it just doesn't work and I don't know why
> either
>
> Jose, how are break points stored? If I know that, next time it happens I
> can have a look and see if they are correct
I'm affraid it's not so easy. The BP are shown in red marked lines in the
code editor, and are passed from the IDE to the program at program's
startup.
In either case, check that the BP is setted in a correct line. I.e. if you
have a sentence, broken in several source lines, then only the last line is
BP suitable. There are also other cases where BP won't work; i.e. lines with
ENDIF, ENDDO, END OBJECT, etc.
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
> Thats pretty much it, sometime it just doesn't work and I don't know why
> either
>
> Jose, how are break points stored? If I know that, next time it happens I
> can have a look and see if they are correct
I'm affraid it's not so easy. The BP are shown in red marked lines in the
code editor, and are passed from the IDE to the program at program's
startup.
In either case, check that the BP is setted in a correct line. I.e. if you
have a sentence, broken in several source lines, then only the last line is
BP suitable. There are also other cases where BP won't work; i.e. lines with
ENDIF, ENDDO, END OBJECT, etc.
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info