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.

WS 2.0: Debugger shows current line wrong

9 posts in General Discussion Last posting was on 2009-04-02 06:42:01.0Z
Pieter Coene Posted on 2008-01-31 11:42:42.0Z
Sender: 5d7e.47a1b251.1804289383@sybase.com
From: Pieter Coene
Newsgroups: sybase.public.workspace.general
Subject: WS 2.0: Debugger shows current line wrong
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <47a1b432.5d9c.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 31 Jan 2008 03:42:42 -0800
X-Trace: forums-1-dub 1201779762 10.22.241.41 (31 Jan 2008 03:42:42 -0800)
X-Original-Trace: 31 Jan 2008 03:42:42 -0800, 10.22.241.41
Lines: 19
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:572
Article PK: 1088261

Hi,

when i debug a stored procedure in WS 2.0, the debug line is
always one row too low (even when creating a breakpoint, it
moves one line down).
I remember having this problem with WS 1.0. This was solved
in WS 1.5 or 1.7 (dont remember exactly).

My specs:
- Adaptive Server Enterprise/15.0.2/EBF 15097 ESD#2/P/NT
(IX86)/Windows 2000/ase1502/2516/32-bit/OPT/Wed Dec 19
19:54:49 2007
- Sybase Workspace 2.0
- Windows XP Professional SP2

Is this known?

Greetz
Pieter


Mike Crocker Posted on 2008-01-31 18:43:17.0Z
From: "Mike Crocker" <crocker@sybase.com>
Newsgroups: sybase.public.workspace.general
References: <47a1b432.5d9c.1681692777@sybase.com>
Subject: Re: WS 2.0: Debugger shows current line wrong
Lines: 36
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <47a216c5$1@forums-1-dub>
Date: 31 Jan 2008 10:43:17 -0800
X-Trace: forums-1-dub 1201804997 10.22.241.152 (31 Jan 2008 10:43:17 -0800)
X-Original-Trace: 31 Jan 2008 10:43:17 -0800, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:574
Article PK: 1088258

Pieter,

Actual breakpoint location could be different from the location of the click
to set the breakpoint. The breakpoint is set on the next line where it is a
valid location to set a breakpoint. But it sounds as if you are seeing
different behavior than what you saw in earlier versions of WorkSpace.

Can you please provide the DDL for your stored procedure or some screen
shots. If you don;t want to post it on the newsgroup you can send it to
mike.crocker@sybase.com.

thanks,
mike

<Pieter Coene> wrote in message news:47a1b432.5d9c.1681692777@sybase.com...
> Hi,
>
> when i debug a stored procedure in WS 2.0, the debug line is
> always one row too low (even when creating a breakpoint, it
> moves one line down).
> I remember having this problem with WS 1.0. This was solved
> in WS 1.5 or 1.7 (dont remember exactly).
>
> My specs:
> - Adaptive Server Enterprise/15.0.2/EBF 15097 ESD#2/P/NT
> (IX86)/Windows 2000/ase1502/2516/32-bit/OPT/Wed Dec 19
> 19:54:49 2007
> - Sybase Workspace 2.0
> - Windows XP Professional SP2
>
> Is this known?
>
> Greetz
> Pieter


Pieter Coene Posted on 2008-02-01 08:33:15.0Z
Sender: 75c3.47a2cc50.1804289383@sybase.com
From: Pieter Coene
Newsgroups: sybase.public.workspace.general
Subject: Re: WS 2.0: Debugger shows current line wrong
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <47a2d94b.7731.1681692777@sybase.com>
References: <47a216c5$1@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 1 Feb 2008 00:33:15 -0800
X-Trace: forums-1-dub 1201854795 10.22.241.41 (1 Feb 2008 00:33:15 -0800)
X-Original-Trace: 1 Feb 2008 00:33:15 -0800, 10.22.241.41
Lines: 17
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:575
Article PK: 1088260

Hi Mike,

i know you can't set a breakpoint on every line, but it
happens in all procedures i have, every valid statement i
click.

As an example, I will send you a screenshot with a simple
statement i try to debug. Notice the line is on the second
line of the statement.

Greetz
Pieter

ps: i couldn't submit my post when attaching a file (IE 7
gives error on the submit-button and Firefox 2.0 gives error
when attaching, saying that it doesn't support attaching
files)


Samir Nigam Posted on 2008-04-09 00:03:22.0Z
Reply-To: "Samir Nigam" <samir_dot_nigam@sybase.com>
From: "Samir Nigam" <samir_dot_nigam@sybase.com>
Newsgroups: sybase.public.workspace.general
References: <47a1b432.5d9c.1681692777@sybase.com>
Subject: Re: WS 2.0: Debugger shows current line wrong
Lines: 30
Organization: Sybase, Inc
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <47fc07ca$1@forums-1-dub>
Date: 8 Apr 2008 17:03:22 -0700
X-Trace: forums-1-dub 1207699402 10.22.241.152 (8 Apr 2008 17:03:22 -0700)
X-Original-Trace: 8 Apr 2008 17:03:22 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:669
Article PK: 1088348

Pieter,

An update on the problem you reported here. We have reproduced the problem
in-house and should have it fixed in the next release of WorkSpace ESD.

Regards,
Samir

<Pieter Coene> wrote in message news:47a1b432.5d9c.1681692777@sybase.com...
> Hi,
>
> when i debug a stored procedure in WS 2.0, the debug line is
> always one row too low (even when creating a breakpoint, it
> moves one line down).
> I remember having this problem with WS 1.0. This was solved
> in WS 1.5 or 1.7 (dont remember exactly).
>
> My specs:
> - Adaptive Server Enterprise/15.0.2/EBF 15097 ESD#2/P/NT
> (IX86)/Windows 2000/ase1502/2516/32-bit/OPT/Wed Dec 19
> 19:54:49 2007
> - Sybase Workspace 2.0
> - Windows XP Professional SP2
>
> Is this known?
>
> Greetz
> Pieter


Tony Brooks Posted on 2008-12-28 13:58:44.0Z
Reply-To: "Tony Brooks" <tony.c.brooks@gmail.com>
From: "Tony Brooks" <tony.c.brooks@gmail.com>
Newsgroups: sybase.public.workspace.general
References: <47a1b432.5d9c.1681692777@sybase.com> <47fc07ca$1@forums-1-dub>
Subject: Re: WS 2.0: Debugger shows current line wrong
Lines: 59
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <49578614@forums-1-dub>
Date: 28 Dec 2008 05:58:44 -0800
X-Trace: forums-1-dub 1230472724 10.22.241.152 (28 Dec 2008 05:58:44 -0800)
X-Original-Trace: 28 Dec 2008 05:58:44 -0800, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:779
Article PK: 1088454

This still does not seem to have been fixed, even in 2.1.

It works ok in 1.7, in that version it shows an extra blank line at the
start of the stored proc and then the breakpoints / line nos seem to be in
sync.

But in later versions, it doesn't show a blank line in the procedure
editor. Then when you add a breakpoint, it tries to move it to the next line
which is often a blank line.

Pretty poor really. Just basic stuff.

Also, in 2.1 it is ridiculously slow when just clicking on a proc to
display it, hangs up for several minutes before displaying it.

This is using ASE 12.5.4.

Not impressed with 2.0 / 2.1. I'm just going to carry on using version 1.7.
It has plenty of flaws, but is just about usable once you learn the
workarounds.

"Samir Nigam" <samir_dot_nigam@sybase.com> wrote in message
news:47fc07ca$1@forums-1-dub...
> Pieter,
>
> An update on the problem you reported here. We have reproduced the problem
> in-house and should have it fixed in the next release of WorkSpace ESD.
>
> Regards,
> Samir
>
> <Pieter Coene> wrote in message
> news:47a1b432.5d9c.1681692777@sybase.com...
>> Hi,
>>
>> when i debug a stored procedure in WS 2.0, the debug line is
>> always one row too low (even when creating a breakpoint, it
>> moves one line down).
>> I remember having this problem with WS 1.0. This was solved
>> in WS 1.5 or 1.7 (dont remember exactly).
>>
>> My specs:
>> - Adaptive Server Enterprise/15.0.2/EBF 15097 ESD#2/P/NT
>> (IX86)/Windows 2000/ase1502/2516/32-bit/OPT/Wed Dec 19
>> 19:54:49 2007
>> - Sybase Workspace 2.0
>> - Windows XP Professional SP2
>>
>> Is this known?
>>
>> Greetz
>> Pieter
>
>


Li huang [Sybase] Posted on 2008-12-30 06:17:20.0Z
Message-ID: <4959BCEE.2040905@sybase.com>
From: "Li huang [Sybase]" <lihuang@sybase.com>
Reply-To: lihuang@sybase.com
Organization: Sybase Software Co., Ltd
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
Newsgroups: sybase.public.workspace.general
To: Tony Brooks <tony.c.brooks@gmail.com>
Subject: Re: WS 2.0: Debugger shows current line wrong
References: <47a1b432.5d9c.1681692777@sybase.com> <47fc07ca$1@forums-1-dub> <49578614@forums-1-dub>
In-Reply-To: <49578614@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Date: 29 Dec 2008 22:17:20 -0800
X-Trace: forums-1-dub 1230617840 10.22.241.152 (29 Dec 2008 22:17:20 -0800)
X-Original-Trace: 29 Dec 2008 22:17:20 -0800, vip152.sybase.com
Lines: 76
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:780
Article PK: 1088451


Tony Brooks wrote:
> This still does not seem to have been fixed, even in 2.1.
>
> It works ok in 1.7, in that version it shows an extra blank line at the
> start of the stored proc and then the breakpoints / line nos seem to be in
> sync.
>
> But in later versions, it doesn't show a blank line in the procedure
> editor. Then when you add a breakpoint, it tries to move it to the next line
> which is often a blank line.
>
> Pretty poor really. Just basic stuff.
>
> Also, in 2.1 it is ridiculously slow when just clicking on a proc to
> display it, hangs up for several minutes before displaying it.
>
> This is using ASE 12.5.4.
>
> Not impressed with 2.0 / 2.1. I'm just going to carry on using version 1.7.
> It has plenty of flaws, but is just about usable once you learn the
> workarounds.
>
>
>
> "Samir Nigam" <samir_dot_nigam@sybase.com> wrote in message
> news:47fc07ca$1@forums-1-dub...
>> Pieter,
>>
>> An update on the problem you reported here. We have reproduced the problem
>> in-house and should have it fixed in the next release of WorkSpace ESD.
>>
>> Regards,
>> Samir
>>
>> <Pieter Coene> wrote in message
>> news:47a1b432.5d9c.1681692777@sybase.com...
>>> Hi,
>>>
>>> when i debug a stored procedure in WS 2.0, the debug line is
>>> always one row too low (even when creating a breakpoint, it
>>> moves one line down).
>>> I remember having this problem with WS 1.0. This was solved
>>> in WS 1.5 or 1.7 (dont remember exactly).
>>>
>>> My specs:
>>> - Adaptive Server Enterprise/15.0.2/EBF 15097 ESD#2/P/NT
>>> (IX86)/Windows 2000/ase1502/2516/32-bit/OPT/Wed Dec 19
>>> 19:54:49 2007
>>> - Sybase Workspace 2.0
>>> - Windows XP Professional SP2
>>>
>>> Is this known?
>>>
>>> Greetz
>>> Pieter
>>
>
>

Hi, Tony:
I can't reproduce it in WorkSpace 2.1. If possible, can you send the sp scripts to me (lihuang@sybase.com). We will look into it.
Thanks a lot!


--
Thanks and regards,

Daniel(Li) Huang [Sybase]

Sybase
Sybase Software (China) Co., Ltd
Room 1202-1203, Building One,
Zhangjiang Semiconductor Industry Park
3000 Longdong Avenue
Pudong, Shanghai 201203
Tel 8621-38657420
Email: lihuang@sybase.com


Tony Brooks Posted on 2008-12-30 12:18:58.0Z
Reply-To: "Tony Brooks" <tony.c.brooks@gmail.com>
From: "Tony Brooks" <tony.c.brooks@gmail.com>
Newsgroups: sybase.public.workspace.general
References: <47a1b432.5d9c.1681692777@sybase.com> <47fc07ca$1@forums-1-dub> <49578614@forums-1-dub> <4959BCEE.2040905@sybase.com>
Subject: Re: WS 2.0: Debugger shows current line wrong
Lines: 110
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <495a11b2@forums-1-dub>
Date: 30 Dec 2008 04:18:58 -0800
X-Trace: forums-1-dub 1230639538 10.22.241.152 (30 Dec 2008 04:18:58 -0800)
X-Original-Trace: 30 Dec 2008 04:18:58 -0800, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:781
Article PK: 1088453


"Li huang [Sybase]" <lihuang@sybase.com> wrote in message
news:4959BCEE.2040905@sybase.com...
> Tony Brooks wrote:
>> This still does not seem to have been fixed, even in 2.1.
>>
>> It works ok in 1.7, in that version it shows an extra blank line at the
>> start of the stored proc and then the breakpoints / line nos seem to be
>> in sync.
>>
>> But in later versions, it doesn't show a blank line in the procedure
>> editor. Then when you add a breakpoint, it tries to move it to the next
>> line
>> which is often a blank line.
>>
>> Pretty poor really. Just basic stuff.
>>
>> Also, in 2.1 it is ridiculously slow when just clicking on a proc to
>> display it, hangs up for several minutes before displaying it.
>>
>> This is using ASE 12.5.4.
>>
>> Not impressed with 2.0 / 2.1. I'm just going to carry on using version
>> 1.7. It has plenty of flaws, but is just about usable once you learn the
>> workarounds.
>>
>>
>>
>> "Samir Nigam" <samir_dot_nigam@sybase.com> wrote in message
>> news:47fc07ca$1@forums-1-dub...
>>> Pieter,
>>>
>>> An update on the problem you reported here. We have reproduced the
>>> problem in-house and should have it fixed in the next release of
>>> WorkSpace ESD.
>>>
>>> Regards,
>>> Samir
>>>
>>> <Pieter Coene> wrote in message
>>> news:47a1b432.5d9c.1681692777@sybase.com...
>>>> Hi,
>>>>
>>>> when i debug a stored procedure in WS 2.0, the debug line is
>>>> always one row too low (even when creating a breakpoint, it
>>>> moves one line down).
>>>> I remember having this problem with WS 1.0. This was solved
>>>> in WS 1.5 or 1.7 (dont remember exactly).
>>>>
>>>> My specs:
>>>> - Adaptive Server Enterprise/15.0.2/EBF 15097 ESD#2/P/NT
>>>> (IX86)/Windows 2000/ase1502/2516/32-bit/OPT/Wed Dec 19
>>>> 19:54:49 2007
>>>> - Sybase Workspace 2.0
>>>> - Windows XP Professional SP2
>>>>
>>>> Is this known?
>>>>
>>>> Greetz
>>>> Pieter
>>>
>>
>>
> Hi, Tony:
> I can't reproduce it in WorkSpace 2.1. If possible, can you send the sp
> scripts to me (lihuang@sybase.com). We will look into it.
> Thanks a lot!
>
>
> --
> Thanks and regards,
>
> Daniel(Li) Huang [Sybase]
>
> Sybase
> Sybase Software (China) Co., Ltd
> Room 1202-1203, Building One,
> Zhangjiang Semiconductor Industry Park
> 3000 Longdong Avenue
> Pudong, Shanghai 201203
> Tel 8621-38657420
> Email: lihuang@sybase.com

Daniel, here is an example... works fine in 1.7 but in 2.1 when you set a
breakpoint eg on the 'select', it moves by itself to the next line which is
blank.
In longer procs, it is then subsequently out of step all the way through.

if exists (select * from sysobjects where name='a1')
drop proc a1
go

create proc a1 as
begin

select getdate()

end
go


Also, in 2.1 when you click on a proc for the first time to open it, the
message 'opening procedural editor' is displayed for several minutes.
This doesn't happen in 1.7. It's a real pain.

Thanks


Li huang [Sybase] Posted on 2009-01-06 08:33:04.0Z
Message-ID: <4963173A.7050308@sybase.com>
From: "Li huang [Sybase]" <lihuang@sybase.com>
Reply-To: lihuang@sybase.com
Organization: Sybase Software Co., Ltd
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
Newsgroups: sybase.public.workspace.general
To: Tony Brooks <tony.c.brooks@gmail.com>
Subject: Re: WS 2.0: Debugger shows current line wrong
References: <47a1b432.5d9c.1681692777@sybase.com> <47fc07ca$1@forums-1-dub> <49578614@forums-1-dub> <4959BCEE.2040905@sybase.com> <495a11b2@forums-1-dub>
In-Reply-To: <495a11b2@forums-1-dub>
Content-Type: multipart/mixed; boundary="------------050001050307070901050505"
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Date: 6 Jan 2009 00:33:04 -0800
X-Trace: forums-1-dub 1231230784 10.22.241.152 (6 Jan 2009 00:33:04 -0800)
X-Original-Trace: 6 Jan 2009 00:33:04 -0800, vip152.sybase.com
Lines: 1559
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:783
Article PK: 1088493


Tony Brooks wrote:
> "Li huang [Sybase]" <lihuang@sybase.com> wrote in message
> news:4959BCEE.2040905@sybase.com...
>> Tony Brooks wrote:
>>> This still does not seem to have been fixed, even in 2.1.
>>>
>>> It works ok in 1.7, in that version it shows an extra blank line at the
>>> start of the stored proc and then the breakpoints / line nos seem to be
>>> in sync.
>>>
>>> But in later versions, it doesn't show a blank line in the procedure
>>> editor. Then when you add a breakpoint, it tries to move it to the next
>>> line
>>> which is often a blank line.
>>>
>>> Pretty poor really. Just basic stuff.
>>>
>>> Also, in 2.1 it is ridiculously slow when just clicking on a proc to
>>> display it, hangs up for several minutes before displaying it.
>>>
>>> This is using ASE 12.5.4.
>>>
>>> Not impressed with 2.0 / 2.1. I'm just going to carry on using version
>>> 1.7. It has plenty of flaws, but is just about usable once you learn the
>>> workarounds.
>>>
>>>
>>>
>>> "Samir Nigam" <samir_dot_nigam@sybase.com> wrote in message
>>> news:47fc07ca$1@forums-1-dub...
>>>> Pieter,
>>>>
>>>> An update on the problem you reported here. We have reproduced the
>>>> problem in-house and should have it fixed in the next release of
>>>> WorkSpace ESD.
>>>>
>>>> Regards,
>>>> Samir
>>>>
>>>> <Pieter Coene> wrote in message
>>>> news:47a1b432.5d9c.1681692777@sybase.com...
>>>>> Hi,
>>>>>
>>>>> when i debug a stored procedure in WS 2.0, the debug line is
>>>>> always one row too low (even when creating a breakpoint, it
>>>>> moves one line down).
>>>>> I remember having this problem with WS 1.0. This was solved
>>>>> in WS 1.5 or 1.7 (dont remember exactly).
>>>>>
>>>>> My specs:
>>>>> - Adaptive Server Enterprise/15.0.2/EBF 15097 ESD#2/P/NT
>>>>> (IX86)/Windows 2000/ase1502/2516/32-bit/OPT/Wed Dec 19
>>>>> 19:54:49 2007
>>>>> - Sybase Workspace 2.0
>>>>> - Windows XP Professional SP2
>>>>>
>>>>> Is this known?
>>>>>
>>>>> Greetz
>>>>> Pieter
>>>
>> Hi, Tony:
>> I can't reproduce it in WorkSpace 2.1. If possible, can you send the sp
>> scripts to me (lihuang@sybase.com). We will look into it.
>> Thanks a lot!
>>
>>
>> --
>> Thanks and regards,
>>
>> Daniel(Li) Huang [Sybase]
>>
>> Sybase
>> Sybase Software (China) Co., Ltd
>> Room 1202-1203, Building One,
>> Zhangjiang Semiconductor Industry Park
>> 3000 Longdong Avenue
>> Pudong, Shanghai 201203
>> Tel 8621-38657420
>> Email: lihuang@sybase.com
>
> Daniel, here is an example... works fine in 1.7 but in 2.1 when you set a
> breakpoint eg on the 'select', it moves by itself to the next line which is
> blank.
> In longer procs, it is then subsequently out of step all the way through.
>
> if exists (select * from sysobjects where name='a1')
> drop proc a1
> go
>
> create proc a1 as
> begin
>
> select getdate()
>
> end
> go
>
>
> Also, in 2.1 when you click on a proc for the first time to open it, the
> message 'opening procedural editor' is displayed for several minutes.
> This doesn't happen in 1.7. It's a real pain.
>
> Thanks
>
>
>
>

Hi, Tony:

I followed your steps and created procedure a1, but can't get the same issue. Please see the attachement.
From WorkSpace 2.0, we enhance procedure editor to add more features (General, Permissions, DDL tabs). It may take more time to load data for
editor in WorkSpace 2.0 than WorkSpace 1.7. Performance enhancements will be available in the next release.

And thanks for your feedback!

--
Thanks and regards,

Daniel(Li) Huang [Sybase]

Sybase
Sybase Software (China) Co., Ltd
Room 1202-1203, Building One,
Zhangjiang Semiconductor Industry Park
3000 Longdong Avenue
Pudong, Shanghai 201203
Tel 8621-38657420
Email: lihuang@sybase.com

pic.JPG

Li huang [Sybase] Posted on 2009-04-02 06:42:01.0Z
Message-ID: <49D45E37.2090807@sybase.com>
From: "Li huang [Sybase]" <lihuang@sybase.com>
Reply-To: lihuang@sybase.com
Organization: Sybase Software Co., Ltd
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
Newsgroups: sybase.public.workspace.general
To: lihuang@sybase.com
CC: Tony Brooks <tony.c.brooks@gmail.com>
Subject: Re: WS 2.0: Debugger shows current line wrong
References: <47a1b432.5d9c.1681692777@sybase.com> <47fc07ca$1@forums-1-dub> <49578614@forums-1-dub> <4959BCEE.2040905@sybase.com> <495a11b2@forums-1-dub> <4963173A.7050308@sybase.com>
In-Reply-To: <4963173A.7050308@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Date: 1 Apr 2009 22:42:01 -0800
X-Trace: forums-1-dub 1238654521 10.22.241.152 (1 Apr 2009 22:42:01 -0800)
X-Original-Trace: 1 Apr 2009 22:42:01 -0800, vip152.sybase.com
Lines: 143
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:837
Article PK: 1088526

Issue'Debugger shows current line wrong' will be fixed in WorkSpace 2.1.2.

Li huang [Sybase] wrote:
> Tony Brooks wrote:
>> "Li huang [Sybase]" <lihuang@sybase.com> wrote in message
>> news:4959BCEE.2040905@sybase.com...
>>> Tony Brooks wrote:
>>>> This still does not seem to have been fixed, even in 2.1.
>>>>
>>>> It works ok in 1.7, in that version it shows an extra blank line at
>>>> the start of the stored proc and then the breakpoints / line nos
>>>> seem to be in sync.
>>>>
>>>> But in later versions, it doesn't show a blank line in the
>>>> procedure editor. Then when you add a breakpoint, it tries to move
>>>> it to the next line
>>>> which is often a blank line.
>>>>
>>>> Pretty poor really. Just basic stuff.
>>>>
>>>> Also, in 2.1 it is ridiculously slow when just clicking on a proc
>>>> to display it, hangs up for several minutes before displaying it.
>>>>
>>>> This is using ASE 12.5.4.
>>>>
>>>> Not impressed with 2.0 / 2.1. I'm just going to carry on using
>>>> version 1.7. It has plenty of flaws, but is just about usable once
>>>> you learn the workarounds.
>>>>
>>>>
>>>>
>>>> "Samir Nigam" <samir_dot_nigam@sybase.com> wrote in message
>>>> news:47fc07ca$1@forums-1-dub...
>>>>> Pieter,
>>>>>
>>>>> An update on the problem you reported here. We have reproduced the
>>>>> problem in-house and should have it fixed in the next release of
>>>>> WorkSpace ESD.
>>>>>
>>>>> Regards,
>>>>> Samir
>>>>>
>>>>> <Pieter Coene> wrote in message
>>>>> news:47a1b432.5d9c.1681692777@sybase.com...
>>>>>> Hi,
>>>>>>
>>>>>> when i debug a stored procedure in WS 2.0, the debug line is
>>>>>> always one row too low (even when creating a breakpoint, it
>>>>>> moves one line down).
>>>>>> I remember having this problem with WS 1.0. This was solved
>>>>>> in WS 1.5 or 1.7 (dont remember exactly).
>>>>>>
>>>>>> My specs:
>>>>>> - Adaptive Server Enterprise/15.0.2/EBF 15097 ESD#2/P/NT
>>>>>> (IX86)/Windows 2000/ase1502/2516/32-bit/OPT/Wed Dec 19
>>>>>> 19:54:49 2007
>>>>>> - Sybase Workspace 2.0
>>>>>> - Windows XP Professional SP2
>>>>>>
>>>>>> Is this known?
>>>>>>
>>>>>> Greetz
>>>>>> Pieter
>>>>
>>> Hi, Tony:
>>> I can't reproduce it in WorkSpace 2.1. If possible, can you send the
>>> sp scripts to me (lihuang@sybase.com). We will look into it.
>>> Thanks a lot!
>>>
>>>
>>> --
>>> Thanks and regards,
>>>
>>> Daniel(Li) Huang [Sybase]
>>>
>>> Sybase
>>> Sybase Software (China) Co., Ltd
>>> Room 1202-1203, Building One,
>>> Zhangjiang Semiconductor Industry Park
>>> 3000 Longdong Avenue
>>> Pudong, Shanghai 201203
>>> Tel 8621-38657420
>>> Email: lihuang@sybase.com
>>
>> Daniel, here is an example... works fine in 1.7 but in 2.1 when you
>> set a breakpoint eg on the 'select', it moves by itself to the next
>> line which is blank.
>> In longer procs, it is then subsequently out of step all the way through.
>>
>> if exists (select * from sysobjects where name='a1')
>> drop proc a1
>> go
>>
>> create proc a1 as
>> begin
>>
>> select getdate()
>>
>> end
>> go
>>
>>
>> Also, in 2.1 when you click on a proc for the first time to open it,
>> the message 'opening procedural editor' is displayed for several minutes.
>> This doesn't happen in 1.7. It's a real pain.
>>
>> Thanks
>>
>>
>>
>>
> Hi, Tony:
>
> I followed your steps and created procedure a1, but can't get the same
> issue. Please see the attachement.
> From WorkSpace 2.0, we enhance procedure editor to add more features
> (General, Permissions, DDL tabs). It may take more time to load data for
> editor in WorkSpace 2.0 than WorkSpace 1.7. Performance enhancements
> will be available in the next release.
>
> And thanks for your feedback!
>
>
> ------------------------------------------------------------------------
>

--
Thanks and regards,

Daniel(Li) Huang [Sybase]

Sybase
Sybase Software (China) Co., Ltd
Room 1202-1203, Building One,
Zhangjiang Semiconductor Industry Park
3000 Longdong Avenue
Pudong, Shanghai 201203
Tel 8621-38657420
Email: lihuang@sybase.com