Ignacio/Jose,
When you are developing or debugging Xailer enhancements, what debugger
do you use to trace through non-xHarbour code? Some of my questions
could be avoided if I could trace through some of the HB API code.
Years ago for assembly and c code, I worked with the IDAPro toolkits and
some third party debugger (forgot the name). IDAPro has a debugger
currently, but the package seems too expensive. Are there some good
alternatives that you have worked with?
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.
What debugger are you using for tracing through C code?
What debugger are you using for tracing through C code?
Never mind, doesn't matter. If you try to pull in some of the xHarbour
..c source to be included in your project, and let Xailer recompile the
source with a Borland -v option injected, then you get an assortment of
compiler errors.
This obviously opens up another can of worms, and is not worth the effort.
I'll just try and work through the ole problems high-level, or use
another language.
On 5/19/2011 2:43 PM, DC wrote:
> Ignacio/Jose,
>
> When you are developing or debugging Xailer enhancements, what debugger
> do you use to trace through non-xHarbour code? Some of my questions
> could be avoided if I could trace through some of the HB API code.
>
> Years ago for assembly and c code, I worked with the IDAPro toolkits and
> some third party debugger (forgot the name). IDAPro has a debugger
> currently, but the package seems too expensive. Are there some good
> alternatives that you have worked with?
>
>
>
>
..c source to be included in your project, and let Xailer recompile the
source with a Borland -v option injected, then you get an assortment of
compiler errors.
This obviously opens up another can of worms, and is not worth the effort.
I'll just try and work through the ole problems high-level, or use
another language.
On 5/19/2011 2:43 PM, DC wrote:
> Ignacio/Jose,
>
> When you are developing or debugging Xailer enhancements, what debugger
> do you use to trace through non-xHarbour code? Some of my questions
> could be avoided if I could trace through some of the HB API code.
>
> Years ago for assembly and c code, I worked with the IDAPro toolkits and
> some third party debugger (forgot the name). IDAPro has a debugger
> currently, but the package seems too expensive. Are there some good
> alternatives that you have worked with?
>
>
>
>