Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

ASA 9 debugger

2 posts in General Discussion Last posting was on 2003-08-11 02:20:13.0Z
Michael Gould Posted on 2003-08-11 00:46:13.0Z
From: "Michael Gould" <mgould@omnicc.com>
Newsgroups: ianywhere.public.general
Subject: ASA 9 debugger
Lines: 23
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Original-NNTP-Posting-Host: adsl-068-209-131-007.sip.jax.bellsouth.net
Message-ID: <3f36e767$1@forums-2-dub>
X-Original-Trace: 10 Aug 2003 17:46:31 -0700, adsl-068-209-131-007.sip.jax.bellsouth.net
NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
Date: 10 Aug 2003 17:46:13 -0700
X-Trace: forums-1-dub 1060562773 10.22.241.42 (10 Aug 2003 17:46:13 -0700)
X-Original-Trace: 10 Aug 2003 17:46:13 -0700, forums-2-dub.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:1554
Article PK: 3783

I just tried out the new debugger in the developers version of ASA 9. While
I like the new layout, this version still suffers the same problem as all
previous debuggers in ASA and makes it very difficult to debug multi-module
stored procedures. I've reported this in both ASA 7 and 8 and was hoping
that 9 would fix this nagging problem.

In the debugger, if during the debug session, a line is processed that has a
error such as a variable label error, or even something like a multi-row
result set returned from a select statement, the debugger falls to the
bottom of that source module instead of staying on the line where the error
occurred. I've never seen this behavior in any other debugger I've used and
it makes it quite difficult to use and find bugs. The proper behavior
should be that the debugger would stay on that line of code and if that
isn't the active window, to switch to that source module and the line of
code where the error happened.

Please fix this... this is a serious problem when trying to debug large
stored procedure modules.

Michael Gould
Omni Computer Consulting, Inc.


Chris Keating (iAnywhere Solutions) Posted on 2003-08-11 02:20:13.0Z
From: "Chris Keating \(iAnywhere Solutions\)" <FightSpam_keating@iAnywhere.com>
Newsgroups: ianywhere.public.general
References: <3f36e767$1@forums-2-dub>
Subject: Re: ASA 9 debugger
Lines: 54
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
NNTP-Posting-Host: surfec007.sybase.com
X-Original-NNTP-Posting-Host: surfec007.sybase.com
Message-ID: <3f36fd5d@forums-1-dub>
Date: 10 Aug 2003 19:20:13 -0700
X-Trace: forums-1-dub 1060568413 199.93.176.7 (10 Aug 2003 19:20:13 -0700)
X-Original-Trace: 10 Aug 2003 19:20:13 -0700, surfec007.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:1555
Article PK: 3784

This is a user forum newsgroup. As such, it should not be used a
communication channel to iAnywhere/Sybase.

Please submit bugs and/or enhancements to Sybase to ensure that it gets the
appropriate attention. Within North America, you can reach Technical Support
by calling 1-800-8SYBASE. If you are located outside of North America, you
can find the contact information for your local Sybase Support Center by
going to the Sybase home page at http://www.sybase.com, clicking on the
"Support" link at the top of the page, and then choosing "Support Centers"
from the left hand frame.

You can always report a bug for free by visiting CaseXpress at
http://casexpress.sybase.com/cx/cx.stm. When submitting calls through
CaseXpress,
please make sure to give an accurate description of the steps you take to
reproduce the bug, and include any files that may be needed (database,
source code) to reproduce the problem.

Enhancements can be submitted at http://www.sybase.com.

/ck

"Michael Gould" <mgould@omnicc.com> wrote in message
news:3f36e767$1@forums-2-dub...
> I just tried out the new debugger in the developers version of ASA 9.
While
> I like the new layout, this version still suffers the same problem as all
> previous debuggers in ASA and makes it very difficult to debug
multi-module
> stored procedures. I've reported this in both ASA 7 and 8 and was hoping
> that 9 would fix this nagging problem.
>
> In the debugger, if during the debug session, a line is processed that has
a
> error such as a variable label error, or even something like a multi-row
> result set returned from a select statement, the debugger falls to the
> bottom of that source module instead of staying on the line where the
error
> occurred. I've never seen this behavior in any other debugger I've used
and
> it makes it quite difficult to use and find bugs. The proper behavior
> should be that the debugger would stay on that line of code and if that
> isn't the active window, to switch to that source module and the line of
> code where the error happened.
>
> Please fix this... this is a serious problem when trying to debug large
> stored procedure modules.
>
> Michael Gould
> Omni Computer Consulting, Inc.
>
>