| Re: I can't clear breakpoints using idlwave_shell [message #37771] |
Wed, 28 January 2004 09:48  |
Alan Barnett
Messages: 5
Registered: November 2001
|
Junior Member |
|
|
On Tue, 27 Jan 2004 23:33:45 -0700, JD Smith wrote:
> On Tue, 27 Jan 2004 17:21:30 -0700, Alan wrote:
>
>> I'm running idl 6.0, idlwave-shell 5.2, gnu emacs 21.2.1 and RH9. I'm
>> having the following problem with breakpoints: If I set a breakpoint at
>> line 18 in file source.pro using C-c C-d C-b, and the message
>>
>> "breakpoint,'source.pro',18
>>
>> appears in the *idl* buffer, but the message
>>
>> "Failed to identify breakponit in idl"
>>
>> appears in the minibuffer.
>>
>> If I then list all the breakpoints, the new breakpoint appears in the
>> list, and if I execute source.pro, execution stops at the new
>> breakpoint, but the line is not marked in the source buffer.
>>
>> If I then try to delete the breakpoint using C-c C-d C-d, I get the
>> message
>>
>> "Cannot identify breakpoint for this line"
>>
>> in the minibuffer, no message in the *idl* buffer, and the breakpoint is
>> not removed.
>> Any ideas how to fix this bug?
>
>
> Sounds like a problem parsing the breakpoint listing, perhaps due to a
> very long or unusual filename. Can you post the breakpoint list?
>
> JD
The problem occurs for all files. An example of the breakpoint list:
IDL> help,/breakpoints
Index Line Attributes File
0 9 Func=FIRST_PT
/home/asb/IDL/spec_dev/first_pt.pro
Here is the source of function first_pt:
;This function extrapolates absolute value the first point of an fid.
function first_pt,xx,$ ;x-coordinate of voxel to extrapolate
yy ;y-coordinate of voxel to extrapolate
COMMON mrsidata
COMMON initcsi
COMMON rsettings
skip=eskip
npts=epts
ndegree=edegree
offset=skip-echo_pt1 ;Extent of extrapolation
data=abs(td_dat1(skip:skip+npts-1,xx,yy)) ;Take absolute value of td data
IF keyword_set(rescale) THEN data=data/data(0)
;Do least square fit to data
xvals=offset+indgen(npts)
weights=data^2
;Linear fit
coeffs=polyfitw(xvals,data,weights,ndegree)
result=coeffs(0)
RETURN,result
END
Before I upgraded to idlwave-shell 5.2 and idl 6.0, the breakpoints
were marked with an "@" sign. This no longer happens. Any other
ideas? Are there any variables that might not be set correctly?
|
|
|
|
| Re: I can't clear breakpoints using idlwave_shell [message #37777 is a reply to message #37771] |
Tue, 27 January 2004 22:33  |
JD Smith
Messages: 850
Registered: December 1999
|
Senior Member |
|
|
On Tue, 27 Jan 2004 17:21:30 -0700, Alan wrote:
> I'm running idl 6.0, idlwave-shell 5.2, gnu emacs 21.2.1 and RH9. I'm
> having the following problem with breakpoints: If I set a breakpoint at
> line 18 in file source.pro using C-c C-d C-b, and the message
>
> "breakpoint,'source.pro',18
>
> appears in the *idl* buffer, but the message
>
> "Failed to identify breakponit in idl"
>
> appears in the minibuffer.
>
> If I then list all the breakpoints, the new breakpoint appears in the
> list, and if I execute source.pro, execution stops at the new
> breakpoint, but the line is not marked in the source buffer.
>
> If I then try to delete the breakpoint using C-c C-d C-d, I get the
> message
>
> "Cannot identify breakpoint for this line"
>
> in the minibuffer, no message in the *idl* buffer, and the breakpoint is
> not removed.
> Any ideas how to fix this bug?
Sounds like a problem parsing the breakpoint listing, perhaps due to a
very long or unusual filename. Can you post the breakpoint list?
JD
|
|
|
|
| Re: I can't clear breakpoints using idlwave_shell [message #37831 is a reply to message #37771] |
Fri, 30 January 2004 12:03 |
JD Smith
Messages: 850
Registered: December 1999
|
Senior Member |
|
|
On Wed, 28 Jan 2004 12:48:59 -0500, Alan Barnett wrote:
> On Tue, 27 Jan 2004 23:33:45 -0700, JD Smith wrote:
>
>> On Tue, 27 Jan 2004 17:21:30 -0700, Alan wrote:
>>
>>> I'm running idl 6.0, idlwave-shell 5.2, gnu emacs 21.2.1 and RH9. I'm
>>> having the following problem with breakpoints: If I set a breakpoint at
>>> line 18 in file source.pro using C-c C-d C-b, and the message
>>>
>>> "breakpoint,'source.pro',18
>>>
>>> appears in the *idl* buffer, but the message
>>>
>>> "Failed to identify breakponit in idl"
>>>
>>> appears in the minibuffer.
>>>
>>> If I then list all the breakpoints, the new breakpoint appears in the
>>> list, and if I execute source.pro, execution stops at the new
>>> breakpoint, but the line is not marked in the source buffer.
>>>
>>> If I then try to delete the breakpoint using C-c C-d C-d, I get the
>>> message
>>>
>>> "Cannot identify breakpoint for this line"
>>>
>>> in the minibuffer, no message in the *idl* buffer, and the breakpoint is
>>> not removed.
>>> Any ideas how to fix this bug?
>>
>>
>> Sounds like a problem parsing the breakpoint listing, perhaps due to a
>> very long or unusual filename. Can you post the breakpoint list?
>>
>> JD
>
> The problem occurs for all files. An example of the breakpoint list:
>
> IDL> help,/breakpoints
> Index Line Attributes File
> 0 9 Func=FIRST_PT
> /home/asb/IDL/spec_dev/first_pt.pro
>
This looks fine.
>
> Before I upgraded to idlwave-shell 5.2 and idl 6.0, the breakpoints
> were marked with an "@" sign. This no longer happens. Any other
> ideas? Are there any variables that might not be set correctly?
I'd bet you only *think* you're using IDLWAVE 5.2, but instead are using
the version bundled with Emacs, 4.7. Try C-h v idlwave-mode-version and
see what it says. If 4.7 (or something less than 5.2), see the FAQ
related to this problem at: http://idlwave.org/idlwave.html#TROUBLE.
The bottom line is that the breakpoint formatting changed in IDL5.5, and
so newer versions of IDLWAVE are needed to work with versions later than
that. It often occurs that you think you've installed and are using a new
version of IDLWAVE, but actually are not. It's easy to fix. The FAQ
addresses this.
JD
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
