[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[List Home]
|
AW: [cobol-dev] Using CBR_ATTACH_TOOL Option
|
- From: "Ahmad Babar" <ababar@xxxxxxxxxx>
- Date: Wed, 29 Jul 2009 09:06:34 +0200
- Delivered-to: cobol-dev@eclipse.org
- Thread-index: AcoQE/QlNgZhMSQURkimzGdXy+bCbgABtqYg
Hello Tetsuya Suehisa,
Yes sure, we are using NetCOBOL for Windows V10.
Thanks
Regards,
Ahmad Babar
-----Ursprüngliche Nachricht-----
Von: cobol-dev-bounces@xxxxxxxxxxx [mailto:cobol-dev-bounces@xxxxxxxxxxx] Im
Auftrag von suehisat
Gesendet: Mittwoch, 29. Juli 2009 08:14
An: cobol-dev@xxxxxxxxxxx
Betreff: Re: [cobol-dev] Using CBR_ATTACH_TOOL Option
Hello Ahmad,
Although the open source COBOL IDE doesn't support remote debug function,
but local attach debug may be possible. I have no way to confirm your
inquiry just now so please give me a few days.
If you are OK, let me know which version of Fujitsu NetCOBOL you
are using. Windows? or Linux?
Best regards,
Tetsuya Suehisa
> Hello Guys,
>
>
>
> If you set the runtime option CBR_ATTACH_TOOL it will invoke the Debugger
> automatically when a COBOL-DLL is called. If that is done so, then the
> normal Fujitsu Debugger from the Project Manager shows up, there is a
> facility to invoke the Eclipse Debugger instead of the common Debugger?
>
> If not, is it may possible to implement this in the next release?
>
> Thanks in advance.
>
>
>
> Ahmad Babar
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> cobol-dev mailing list
> cobol-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cobol-dev
>
>
>
_______________________________________________
cobol-dev mailing list
cobol-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cobol-dev
__________ NOD32 4286 (20090728) Information __________
Diese E-Mail wurde vom NOD32 antivirus system gepr|ft
http://www.nod32.com