Hi folks:
can I work with both debuggers in the same installation?

Beling
TIA

How and why? What shall it make a sense to debug a program with 2 debuggers
at the same time? On the other hand, debugging either with the VX-IDE or at
other time with xppdbg is no problem.
Klemens

"Carlos Beling" <beling@uai.com.br> schrieb im Newsbeitrag
news:j9U4$BjzDHA.1976@S15147418...
> Hi folks:
> can I work with both debuggers in the same installation?
>
> Beling
> TIA
>

Carlos Beling wrote:

> Hi folks:
> can I work with both debuggers in the same installation?
> 
> Beling
> TIA

Yes. Xppdbg.exe still works, allthough we are very shure
that everybody who tried the VX integrated debugger won't 
see a reason to use the old one 

Another point: Time will come when xppdbg will no longer
be maintained.

Regards


Andreas Herdt


//////////////////////////////////////////////////////////////////
//
// Alaska Research & Development
// Homepage: www.alaska-research.com
// Newsgroup: nntp://news.alaska-Software.net
//
//////////////////////////////////////////////////////////////////

Hi Andreas:
many thanks. I'm thinking in using it only when VX is in pre-release.

Beling
Happy New Year

Andreas Herdt wrote:
> Carlos Beling wrote:
> 
> 
>>Hi folks:
>>can I work with both debuggers in the same installation?
>>
>>Beling
>>TIA
> 
> 
> Yes. Xppdbg.exe still works, allthough we are very shure
> that everybody who tried the VX integrated debugger won't 
> see a reason to use the old one 
> 
> Another point: Time will come when xppdbg will no longer
> be maintained.
>

Carlos Beling wrote:

> Hi Andreas:
> many thanks. I'm thinking in using it only when VX is in pre-release.

Yea, know what you mean. The first steamship still had sails.
Just in case...
 
> Beling
> Happy New Year

Same to you.

Regards


Andreas Herdt


//////////////////////////////////////////////////////////////////
//
// Alaska Research & Development
// Homepage: www.alaska-research.com
// Newsgroup: nntp://news.alaska-Software.net
//
//////////////////////////////////////////////////////////////////

Carlos
At least the debugger it's excellent,  even in prerelease. After that i don't think that i will use the terminal debugger again.

Regards
Mike Evans

"Carlos Beling" <beling@uai.com.br> wrote in message news:J%23ispVszDHA.1976@S15147418...
> Hi Andreas:
> many thanks. I'm thinking in using it only when VX is in pre-release.
>
> Beling
> Happy New Year
>
> Andreas Herdt wrote:
> > Carlos Beling wrote:
> >
> >
> >>Hi folks:
> >>can I work with both debuggers in the same installation?
> >>
> >>Beling
> >>TIA
> >
> >
> > Yes. Xppdbg.exe still works, allthough we are very shure
> > that everybody who tried the VX integrated debugger won't
> > see a reason to use the old one 
> >
> > Another point: Time will come when xppdbg will no longer
> > be maintained.
> >
>

Hello Andreas,

can the VX debugger only work with the projects opened or created with the
VX ?
Or is it possible to debug a xbase++ main.exe created out of the VX like now
we do with xppdbg ?

The problem that we have is that the enviroment to create our main.exe/dlls
is so complex (as you probably
remember) that now they can not be reproduced within the VX, but we would
like to use the debugger of the VX
because we suppose is better than the old one (as you said).

Regards,
Luciano


"Andreas Herdt" <andreas.herdt@alaska-research.com> wrote in message
news:GoK$gxlzDHA.1972@S15147418...
> Carlos Beling wrote:
>
> > Hi folks:
> > can I work with both debuggers in the same installation?
> >
> > Beling
> > TIA
>
> Yes. Xppdbg.exe still works, allthough we are very shure
> that everybody who tried the VX integrated debugger won't
> see a reason to use the old one 
>
> Another point: Time will come when xppdbg will no longer
> be maintained.
>
> -- 
> Regards
>
>
> Andreas Herdt
>
>
> //////////////////////////////////////////////////////////////////
> 
>  Alaska Research & Development
>  Homepage: www.alaska-research.com
>  Newsgroup: nntp://news.alaska-Software.net
> 
> //////////////////////////////////////////////////////////////////

"Luciano" <cisnado@ipcgmbh.com> wrote in message
news:jpn71aH1DHA.2016@S15147418...
> Hello Andreas,
>
> can the VX debugger only work with the projects opened or created with the
> VX ? Or is it possible to debug a xbase++ main.exe created out of the VX
like
> now we do with xppdbg ?
(...)

Luciano,

you can debug any Xbase++ executable within Visual Xbase++.  If you
can't load your project into the IDE for the reasons you stated, try this:

  vx20 <yourEXE>.

Another way is to use the "Open" dialog (set the file type to executable).
If no project is loaded for debugging, a default project is created for
you for maintaining breakpoint and other debugging session information.

Regards,
  Till

--
---------------------------------------------------
ARD - Alaska Research & Development

Web:       http://www.alaska-research.com
Investors: http://www.alaska-research.com/tifund
E-Mail:    mailto:till.warweg@alaska-research.com
Contact:   mailto:info@alaska-research.com
---------------------------------------------------

Till,

> you can debug any Xbase++ executable within Visual Xbase++.

...compiled with 1.82.294

Regards,

Phil Ide

***************************************
* Xbase++ FAQ, Libraries and Sources: *
* goto: http://www.idep.org.uk/xbase  *
***************************************

Spendthrift: Negative saver

"Phil Ide" <phil@idep.org.uk> wrote in message
news:719drbvmxrhv$.dlg@idep.org.uk...

> > you can debug any Xbase++ executable within Visual Xbase++.
>
> ...compiled with 1.82.294

You're right.

Thanks,
   Till

--
---------------------------------------------------
ARD - Alaska Research & Development

Web:       http://www.alaska-research.com
Investors: http://www.alaska-research.com/tifund
E-Mail:    mailto:till.warweg@alaska-research.com
Contact:   mailto:info@alaska-research.com
---------------------------------------------------

Hello Till,

Thanks for your help !! The vx20 <yourEXE> works ok and the debugger is
definitly much better than the old one.

But after the debugger stops in the first prg, how can i set a break point
in another prg ?
for example like before we did it in the old debugger: we used the File/Open
module command
from the menu, select the desired prg and set the break point. The problem
is that using the vx20 <yourEXE>
it seems i do NOT HAVE all prgs at once available (as when i have an opened
project),
do i ?

I do not want to press F10 until the desired prg is available because it can
take a lot of time. I would like
to run the program and go to a previous selected break point directly.

Regards
Luciano


"Till Warweg" <till.warweg@alaska-research.com> wrote in message
news:EFAu8WI1DHA.3616@S15147418...
> "Luciano" <cisnado@ipcgmbh.com> wrote in message
> news:jpn71aH1DHA.2016@S15147418...
> > Hello Andreas,
> >
> > can the VX debugger only work with the projects opened or created with
the
> > VX ? Or is it possible to debug a xbase++ main.exe created out of the VX
> like
> > now we do with xppdbg ?
> (...)
>
> Luciano,
>
> you can debug any Xbase++ executable within Visual Xbase++.  If you
> can't load your project into the IDE for the reasons you stated, try this:
>
>   vx20 <yourEXE>.
>
> Another way is to use the "Open" dialog (set the file type to executable).
> If no project is loaded for debugging, a default project is created for
> you for maintaining breakpoint and other debugging session information.
>
> Regards,
>   Till
>
> --
> ---------------------------------------------------
> ARD - Alaska Research & Development
>
> Web:       http://www.alaska-research.com
> Investors: http://www.alaska-research.com/tifund
> E-Mail:    mailto:till.warweg@alaska-research.com
> Contact:   mailto:info@alaska-research.com
> ---------------------------------------------------
>
>
>

Hi Luciano

Luciano wrote:
> Hello Till,
> 
> Thanks for your help !! The vx20 <yourEXE> works ok and the debugger is
> definitly much better than the old one.
> 
> But after the debugger stops in the first prg, how can i set a break point
> in another prg ?
> for example like before we did it in the old debugger: we used the File/Open
> module command
> from the menu, select the desired prg and set the break point. The problem
> is that using the vx20 <yourEXE>
> it seems i do NOT HAVE all prgs at once available (as when i have an opened
> project),
> do i ?

Yes you do just open the PRG from the explorer window and mark the new 
breakpoint.

> 
> I do not want to press F10 until the desired prg is available because it can
> take a lot of time. I would like
> to run the program and go to a previous selected break point directly.

Try the stepout option its in the menu (no hot key is defined). This 
will stepout of the current function. Note I agree that there needs to 
be some sort of coninue execution function like F5 in the old debuger.

Jim

> 
> Regards
> Luciano
> 
> 
> "Till Warweg" <till.warweg@alaska-research.com> wrote in message
> news:EFAu8WI1DHA.3616@S15147418...
> 
>>"Luciano" <cisnado@ipcgmbh.com> wrote in message
>>news:jpn71aH1DHA.2016@S15147418...
>>
>>>Hello Andreas,
>>>
>>>can the VX debugger only work with the projects opened or created with
> 
> the
> 
>>>VX ? Or is it possible to debug a xbase++ main.exe created out of the VX
>>
>>like
>>
>>>now we do with xppdbg ?
>>
>>(...)
>>
>>Luciano,
>>
>>you can debug any Xbase++ executable within Visual Xbase++.  If you
>>can't load your project into the IDE for the reasons you stated, try this:
>>
>>  vx20 <yourEXE>.
>>
>>Another way is to use the "Open" dialog (set the file type to executable).
>>If no project is loaded for debugging, a default project is created for
>>you for maintaining breakpoint and other debugging session information.
>>
>>Regards,
>>  Till
>>
>>--
>>---------------------------------------------------
>>ARD - Alaska Research & Development
>>
>>Web:       http://www.alaska-research.com
>>Investors: http://www.alaska-research.com/tifund
>>E-Mail:    mailto:till.warweg@alaska-research.com
>>Contact:   mailto:info@alaska-research.com
>>---------------------------------------------------
>>
>>
>>
> 
> 
>

"James Loughner" <jwrl@charter.net> wrote in Message
news:oPrYQuT1DHA.2012@S15147418...
> > I do not want to press F10 until the desired prg is available because it
can
> > take a lot of time. I would like
> > to run the program and go to a previous selected break point directly.
>
> Try the stepout option its in the menu (no hot key is defined). This
> will stepout of the current function. Note I agree that there needs to
> be some sort of coninue execution function like F5 in the old debuger.

Sorry, folks, you've lost me here...

The old debugger assigned "GO" to the F5 key. The equivalent in VX
is Run -> Run <target>. This implicitly loads the executable into the
debugger if debugging info had been compiled into the project. Similar
to "GO", execution halts at the first breakpoint, error or QUIT .

Having said all that, why is it that I have this feeling that's not what you
were talking about...??

One more thing. Jim, regarding "Step Out", you are right; there's currently
no shortcut key defined. However, may define your own shortcut using
Tools -> Customize.

Regards,
  Till
  [Alaska Research & Development]

Hi Till

Till Warweg wrote:
> "James Loughner" <jwrl@charter.net> wrote in Message
> news:oPrYQuT1DHA.2012@S15147418...
> 
>>>I do not want to press F10 until the desired prg is available because it
> 
> can
> 
>>>take a lot of time. I would like
>>>to run the program and go to a previous selected break point directly.
>>
>>Try the stepout option its in the menu (no hot key is defined). This
>>will stepout of the current function. Note I agree that there needs to
>>be some sort of coninue execution function like F5 in the old debuger.
> 
> 
> Sorry, folks, you've lost me here...
> 
> The old debugger assigned "GO" to the F5 key. The equivalent in VX
> is Run -> Run <target>. This implicitly loads the executable into the
> debugger if debugging info had been compiled into the project. Similar
> to "GO", execution halts at the first breakpoint, error or QUIT .
> 
> Having said all that, why is it that I have this feeling that's not what you
> were talking about...??

Ok now the debugger is stopped at a break. I now want to continue 
running the code. How is this done? In the old debugger F5 would start 
execution from the break. Run restarts the execution from the beginning. 
Some times I would like to move through a loop. ie

FOR I = 1 TO big number
    ALTD()   break
    doalotofstuff
NEXT I

In the old debugger F5 would strat the program and then stop again at 
the break so I could examine values. I don't want to have to step 
through the doalotofstuff code.


> 
> One more thing. Jim, regarding "Step Out", you are right; there's currently
> no shortcut key defined. However, may define your own shortcut using
> Tools -> Customize.

I figured that out. I used CTRL-F5

> 
> Regards,
>   Till
>   [Alaska Research & Development]
> 
>

Hello Till,

James is totally right, we need the same functionality like the F5 in the
old debugger. I agree. His explanation is very good.

Regards
Luciano


"James Loughner" <jwrl@charter.net> schrieb im Newsbeitrag
news:NEwREtY1DHA.3616@S15147418...
>
> Hi Till
>
> Till Warweg wrote:
> > "James Loughner" <jwrl@charter.net> wrote in Message
> > news:oPrYQuT1DHA.2012@S15147418...
> >
> >>>I do not want to press F10 until the desired prg is available because
it
> >
> > can
> >
> >>>take a lot of time. I would like
> >>>to run the program and go to a previous selected break point directly.
> >>
> >>Try the stepout option its in the menu (no hot key is defined). This
> >>will stepout of the current function. Note I agree that there needs to
> >>be some sort of coninue execution function like F5 in the old debuger.
> >
> >
> > Sorry, folks, you've lost me here...
> >
> > The old debugger assigned "GO" to the F5 key. The equivalent in VX
> > is Run -> Run <target>. This implicitly loads the executable into the
> > debugger if debugging info had been compiled into the project. Similar
> > to "GO", execution halts at the first breakpoint, error or QUIT .
> >
> > Having said all that, why is it that I have this feeling that's not what
you
> > were talking about...??
>
> Ok now the debugger is stopped at a break. I now want to continue
> running the code. How is this done? In the old debugger F5 would start
> execution from the break. Run restarts the execution from the beginning.
> Some times I would like to move through a loop. ie
>
> FOR I = 1 TO big number
>     ALTD()   break
>     doalotofstuff
> NEXT I
>
> In the old debugger F5 would strat the program and then stop again at
> the break so I could examine values. I don't want to have to step
> through the doalotofstuff code.
>
>
> >
> > One more thing. Jim, regarding "Step Out", you are right; there's
currently
> > no shortcut key defined. However, may define your own shortcut using
> > Tools -> Customize.
>
> I figured that out. I used CTRL-F5
>
> >
> > Regards,
> >   Till
> >   [Alaska Research & Development]
> >
> >
>

Jim,

please note that I've just realised that I misspelled the command
name in my last post:

"The equivalent in VX is Run -> Run <target>" should actually read
"The equivalent in VX is Run -> DEBUG <target>".

Sorry about that.

> Ok now the debugger is stopped at a break. I now want to continue
> running the code. How is this done?

Just press F9 (Debug <target>) again.

> Some times I would like to move through a loop. ie
>
> FOR I = 1 TO big number
>     ALTD()   break
>     doalotofstuff
> NEXT I
>
> In the old debugger F5 would strat the program and then stop again at
> the break so I could examine values. I don't want to have to step
> through the doalotofstuff code.

Please let's be clear on this: F9 doesn't in your case??
Debug <target> should behave exactly the same as "GO" in the text
mode debugger in that respect. I've just debugged the code snippet
you sent and execution stopped on ALTD() each time I hit F9?
Same behaviour with normal breakpoints.

> (Tools -> Customize)
> I figured that out. I used CTRL-F5



Regards,
  Till

--
---------------------------------------------------
ARD - Alaska Research & Development

Web:       http://www.alaska-research.com
Investors: http://www.alaska-research.com/tifund
E-Mail:    mailto:till.warweg@alaska-research.com
Contact:   mailto:info@alaska-research.com
---------------------------------------------------

Ok Till, but that was not obvious to me. I'll try it.

Jim

Till Warweg wrote:

> Jim,
> 
> please note that I've just realised that I misspelled the command
> name in my last post:
> 
> "The equivalent in VX is Run -> Run <target>" should actually read
> "The equivalent in VX is Run -> DEBUG <target>".
> 
> Sorry about that.
> 
> 
>>Ok now the debugger is stopped at a break. I now want to continue
>>running the code. How is this done?
> 
> 
> Just press F9 (Debug <target>) again.
> 
> 
>>Some times I would like to move through a loop. ie
>>
>>FOR I = 1 TO big number
>>    ALTD()   break
>>    doalotofstuff
>>NEXT I
>>
>>In the old debugger F5 would strat the program and then stop again at
>>the break so I could examine values. I don't want to have to step
>>through the doalotofstuff code.
> 
> 
> Please let's be clear on this: F9 doesn't in your case??
> Debug <target> should behave exactly the same as "GO" in the text
> mode debugger in that respect. I've just debugged the code snippet
> you sent and execution stopped on ALTD() each time I hit F9?
> Same behaviour with normal breakpoints.
> 
> 
>>(Tools -> Customize)
>>I figured that out. I used CTRL-F5
> 
> 
> 
> 
> Regards,
>   Till
> 
> --
> ---------------------------------------------------
> ARD - Alaska Research & Development
> 
> Web:       http://www.alaska-research.com
> Investors: http://www.alaska-research.com/tifund
> E-Mail:    mailto:till.warweg@alaska-research.com
> Contact:   mailto:info@alaska-research.com
> ---------------------------------------------------
> 
> 
>