Bug: (void-variable jde-ant-interactive-args-history)

Description:

 

I just began using Ant with the JDEE.  I encountered the stack trace below when I enabled the "Jde Ant Read Args" option in the customization buffers.  The argument history is not initialized for the first attempted jde-ant-build and the stack trace is the result.  I went and hacked my prj.el file as seen below to include a setq that initializes the variable to a list containing the null string.  That fixed the problem.

 

I'm not ready to take the plunge and try to delve JDEE lisp code and make a better fix with my 7 years rusty CSC301 Scheme memories, .  And the error could be a configuration error on my part.

 

Hope this is the right place to put this post,

Elo

 

ps.  I did try searching the list archive for this issue and did not see it, which is why I went ahead with this post.

 

Backtrace:

 

Debugger entered--Lisp error: (void-variable jde-ant-interactive-args-history)
  (nth 0 jde-ant-interactive-args-history)
  (read-from-minibuffer "Additional build args: " (nth 0 jde-ant-interactive-args-history) nil nil (quote (jde-ant-interactive-args-history . 1)))
  (setq interactive-args (read-from-minibuffer "Additional build args: " (nth 0 jde-ant-interactive-args-history) nil nil (quote ...)))
  (if jde-ant-read-args (setq interactive-args (read-from-minibuffer "Additional build args: " ... nil nil ...)))
  (let (buildfile history target interactive-args) (setq buildfile (jde-ant-interactive-get-buildfile)) (setq history (jde-ant-get-from-history buildfile)) (if jde-ant-read-target (if jde-ant-complete-target ... ...)) (jde-ant-add-to-history buildfile history) (setq target (jde-ant-escape target)) (if jde-ant-read-args (setq interactive-args ...)) (setq jde-ant-interactive-buildfile buildfile) (list buildfile target interactive-args))
  call-interactively(jde-ant-build)
  jde-build()
* call-interactively(jde-build)

 

prj.el contents:

 

;; ${CODE_SRC}, etc. are Windows environment variables set to F:\code\src, etc.

 

(jde-project-file-version "1.0")
(jde-set-variables
 '(jde-javadoc-gen-destination-directory "${CODE_DOCS}")
 '(jde-ant-enable-find t)
 '(jde-global-classpath (quote ("${CODE_CLASSES}")))
 '(jde-compile-option-directory "${CODE_CLASSES}")
 '(jde-build-function (quote (jde-ant-build)))
 '(jde-sourcepath (quote ("${CODE_SRC}")))
 '(jde-ant-read-args t))

 

;; Hack.  jde-ant-build requires an initial value and it backtraces without this.
(setq jde-ant-interactive-args-history '(""))

Host platform:  Windows XP Home Edition.

JDEE version:  2.3.2

Emacs version:  21.2.1

 

Re: Bug: (void-variable jde-ant-interactive-args-history)

"Elo" <elo <at> drizzle.com> writes:
This has been fixed in CVS.

Just grab the latest jde-ant.el from CVS, it has several bug fixes.

Javier

> Description:
> 
>  
> 
> I just began using Ant with the JDEE.  I encountered the stack trace below
> when I enabled the "Jde Ant Read Args" option in the customization buffers. 
> The argument history is not initialized for the first attempted jde-ant-build
> and the stack trace is the result.  I went and hacked my prj.el file as seen
> below to include a setq that initializes the variable to a list containing the
> null string.  That fixed the problem.
> 
>  
> 
> I'm not ready to take the plunge and try to delve JDEE lisp code and make a
> better fix with my 7 years rusty CSC301 Scheme memories, .  And the error
> could be a configuration error on my part.
> 
>  
> 
> Hope this is the right place to put this post,
> 
> Elo
> 
>  
> 
> ps.  I did try searching the list archive for this issue and did not see it,
> which is why I went ahead with this post.
> 
>  
> 
> Backtrace:
> 
>  
> 
> Debugger entered--Lisp error: (void-variable jde-ant-interactive-args-history)
>   (nth 0 jde-ant-interactive-args-history)
>   (read-from-minibuffer "Additional build args: " (nth 0
> jde-ant-interactive-args-history) nil nil (quote
> (jde-ant-interactive-args-history . 1)))
>   (setq interactive-args (read-from-minibuffer "Additional build args: " (nth
> 0 jde-ant-interactive-args-history) nil nil (quote ...)))
>   (if jde-ant-read-args (setq interactive-args (read-from-minibuffer
> "Additional build args: " ... nil nil ...)))
>   (let (buildfile history target interactive-args) (setq buildfile
> (jde-ant-interactive-get-buildfile)) (setq history (jde-ant-get-from-history
> buildfile)) (if jde-ant-read-target (if jde-ant-complete-target ... ...))
> (jde-ant-add-to-history buildfile history) (setq target (jde-ant-escape
> target)) (if jde-ant-read-args (setq interactive-args ...)) (setq
> jde-ant-interactive-buildfile buildfile) (list buildfile target
> interactive-args))
>   call-interactively(jde-ant-build)
>   jde-build()
> * call-interactively(jde-build)
> 
>  
> 
> prj.el contents:
> 
>  
> 
> ;; ${CODE_SRC}, etc. are Windows environment variables set to F:\code\src,
> etc.
> 
>  
> 
> (jde-project-file-version "1.0")
> (jde-set-variables
>  '(jde-javadoc-gen-destination-directory "${CODE_DOCS}")
>  '(jde-ant-enable-find t)
>  '(jde-global-classpath (quote ("${CODE_CLASSES}")))
>  '(jde-compile-option-directory "${CODE_CLASSES}")
>  '(jde-build-function (quote (jde-ant-build)))
>  '(jde-sourcepath (quote ("${CODE_SRC}")))
>  '(jde-ant-read-args t))
> 
>  
> 
> ;; Hack.  jde-ant-build requires an initial value and it backtraces without
> this.
> (setq jde-ant-interactive-args-history '(""))
> 
> Host platform:  Windows XP Home Edition.
> 
> JDEE version:  2.3.2
> 
> Emacs version:  21.2.1
> 
>  
> 

--

-- 

help on installing jde....

Hi,

I'm trying to install jde. I get to jdee page, and the link to download jdee, 
opens a page full of links to files. I should be ashamed of saying this, but I 
don't know what to download from there !

I found and downloaded and rpm on sourceforge. Besides I downloaded the files 
it says there have to be installed previous to install jde, aka eieio, 
speedbar, semantics, elib and ede. In the installaion guide this is rather 
vague explained. An order is no specified  there, neither how to install.

I run makes for could install eieio and speedbar, but semantics fails.. and 
from here on, I get stoped.

Could anybody please tell me something about this installation process, what 
goes first, how... 

I'm pretty new on linux, and still not very well acquainted with 
installations, packages...tars..etc.

I'll appreciate very much any help me in any way

Thanks a bunch,

Andrew

Re: help on installing jde....

Try Artur Hefczyc's fetch-and-install-jde script.  It can be downloaded from:

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/wttools/wttools/emacs-stuff/install-jde.sh?rev=1.8&content-type=text/plain

It automates fetching and installing all the bits, except for the Java Developers Kit.

You probably should remove what you have installed before running this script.

Dave F

> Hi,
> 
> I'm trying to install jde. I get to jdee page, and the link to download jdee,
>  
> opens a page full of links to files. I should be ashamed of saying this, but 
> I 
> don't know what to download from there !
> 
> I found and downloaded and rpm on sourceforge. Besides I downloaded the files
>  
> it says there have to be installed previous to install jde, aka eieio, 
> speedbar, semantics, elib and ede. In the installaion guide this is rather 
> vague explained. An order is no specified  there, neither how to install.
> 
> I run makes for could install eieio and speedbar, but semantics fails.. and 
> from here on, I get stoped.
> 
> Could anybody please tell me something about this installation process, what 
> goes first, how... 
> 
> I'm pretty new on linux, and still not very well acquainted with 
> installations, packages...tars..etc.
> 
> 
> I'll appreciate very much any help me in any way
> 
> Thanks a bunch,
> 
> 
> Andrew

Re: help on installing jde....

Hello,

As author of this script I can also recommend it for automatic installation
of JDEE and all necessary components. I am also good in Linux environment
so if you have any problems feel free to send questions.
I work with JDEE+emacs on both Windows and Linux so for most
problems I have solutions.

good luck
Artur Hefczyc

> Try Artur Hefczyc's fetch-and-install-jde script.  It can be downloaded
from:
>
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/wttools/wttools/em
acs-stuff/install-jde.sh?rev=1.8&content-type=text/plain
> It automates fetching and installing all the bits, except for the Java
Developers Kit.
> You probably should remove what you have installed before running this
script.
> Dave F
> > I'm trying to install jde. I get to jdee page, and the link to download
jdee,
> > opens a page full of links to files. I should be ashamed of saying this,
but
> > I don't know what to download from there !
> > I found and downloaded and rpm on sourceforge. Besides I downloaded the
files
> > it says there have to be installed previous to install jde, aka eieio,
> > speedbar, semantics, elib and ede. In the installaion guide this is
rather
> > vague explained. An order is no specified  there, neither how to
install.
> > I run makes for could install eieio and speedbar, but semantics fails..
and
> > from here on, I get stoped.
> > Could anybody please tell me something about this installation process,
what
> > goes first, how...
> > I'm pretty new on linux, and still not very well acquainted with
> > installations, packages...tars..etc.
--
Artur Hefczyc
http://wttools.sf.net/

Re: Newbie has been stuck for weeks tryig to get stop on breakpoint.

I updated to the latest JDE, 2.3.2.  All other setting and version info 
is as below.

During one try out of about twenty, the breakpoint functionality worked 
and the green line turned red.  But I can't isolate the conditions under 
which it worked . . . throwing darts in the dark.  During the other 
times, the JDE behaved as described below.  I did try setting 'suspend' 
to 'y', but that seemed to just delay things.

What are the steps I should take to make sure that the debugger stops at 
breakpoints?  

Thank you in advance,
   - CB

Jack Donohue wrote:

> When you set the breakpoint, does the line turn red? Or green?
>
> Christopher Mark Balz wrote:
>
>> I've been posting once every 10 days for weeks, and hope someone can 
>> point me in the right direction.
>>
>> Problem:
>> -------
>> Not able to get any use out of jdebug yet.
>>
>> With What:
>> ---------
>> Windows 2000 Service Pack 3, Java 1.4 SDK, Tomcat 3.3 Servlet Engine, 
>> GNU Emacs 21.2.1, JDE 2.2.8, a web application that I'm trying to 
>> debug, compiled with -g option, running Tomcat from startup.bat with 
>> normal successful operation, have TOMCAT_OPTS set to:
>>     -Xdebug -Xnoagent 
>> -Xrunjdwp:transport=dt_socket,address=6001,server=y,suspend=n
>>
>> Description:
>> -----------
>> I've gotten as far as successfully attaching to the Tomcat (v3.3) 
>> Server process.  See below for output.  The web application that I am 
>> trying to debug does not seem to stop at the breakpoint I set.  When 
>> I try to Display->Variable, I get an obscure error message referring 
>> to an 'unbound slot'.
>>
>> Other Stuff that May Matter:
>> ---------------------------
>> On the JDE FAQ page, I noticed that it recommended starting the web 
>> server from the JDE.  Since tomcat.bat and tomcat.sh are a few 
>> hundred lines long, I don't know if this is the best option.  Is it 
>> necessary?
>>
>> I found the simplified Tomcat startup commands in startup.sh, created 
>> a project file, and set the variables indicated in the FAQ entry.  
>> But then on JDE->Run App, it used javaw (?I am not using AWT) and the 
>> -v option, which crashed the starting of the vm.  Any comments?
>>
>> Thank You in Advance!
>> --------------------
>>
>> Debugger Output
>> ---------------
>>
>> *** Debugger Output for Process 6001(1) ***
>>
>> Attached to process on port 6001 of local host.
>> Attached VM (socket) Java Debug Interface (Reference Implementation) 
>> version 1.4
>> Java Debug Wire Protocol (Reference Implementation) version 1.4
>> JVM Debug Interface version 1.2
>> JVM version 1.4.0 (Java HotSpot(TM) Client VM, mixed mode)
>> Running 6001.
>> Setting breakpoint at line 390 in QueryOutput.java.
>> Resolved breakpoint set in QueryOutput.java at line 390.
>> Cleared breakpoint at line 390 in file QueryOutput.java
>> Setting breakpoint at line 390 in QueryOutput.java.
>> Resolved breakpoint set in QueryOutput.java at line 390.
>
>

--

-- 
". . . / This Cabinet is formd of Gold / And Pearl & Crystal shining bright
And within it opens into a World / . . .
Another England there I saw / Another London with its Tower
Another Thames & other Hills / And another pleasant Surrey Bower
. . ."
- from "The Crystal Cabinet", a poem by William Blake.

RE: Newbie has been stuck for weeks tryig to get stop on breakpoint.

Hi,

I don't really have a definite solution to your problem, but I did some
work on the Java side of JDEbug last year, and its behaviour is a bit
unreliable. Paul is working on integrating the work that I did and even
more importantly, on improving the communication between the Emacs side
of JDE and the Java VM that handles the debugging. One possible, and
likely, explanation to your problem is that due to a threading problem
in the Emacs/Java communication, Emacs misses some event messages from
the debugger.

Basically, the steps that should be followed are:

1. Breakpoints (file, line) are specified in Emacs and sent to the Java
side
2. Whenever the class loader loads a class, it is checked to see if it
matches a breakpoint. If so, the breakpoint is resolved, meaning that
the VM will suspend execution at that point and generate a "breakpoint
hit" event. When the breakpoint is resolved, its colour is changed in
the code.
3. Whenever there is such an event, it is sent from the Java side to
Emacs, and Emacs should display the correct file and line.

When I was working on it, the most common problem was that the
resolution of breakpoints didn't succeed, or succeeded only after the
program execution had already passed the actual breakpoint. I believe
that I corrected a bug or two there, but that has probably not yet been
included. I also seem to remember that the sequence of setting
breakpoints, starting debugger, etc., was very important, but you seem
to be getting the "breakpoint resolved" messages, so you should be all
right there.

If I remember right, there should be a *jdebug* buffer, maybe that and
this description will help you find a clue. It's been a little while
since I worked on this, so I don't remember exactly how things worked.
Anyway, I think we can all look forward to a major improvement to JDEbug
pretty soon.

/ Petter

> -----Original Message-----
> From: Christopher Mark Balz [mailto:ChristopherBalz <at> yahoo.com] 
> Sent: den 3 februari 2003 06:25
> To: Jack Donohue; ahyatt <at> intraspect.com; jde <at> sunsite.dk
> Subject: Re: Newbie has been stuck for weeks tryig to get 
> stop on breakpoint.
> 
> 
> I updated to the latest JDE, 2.3.2.  All other setting and 
> version info 
> is as below.
> 
> During one try out of about twenty, the breakpoint 
> functionality worked 
> and the green line turned red.  But I can't isolate the 
> conditions under 
> which it worked . . . throwing darts in the dark.  During the other 
> times, the JDE behaved as described below.  I did try setting 
> 'suspend' 
> to 'y', but that seemed to just delay things.
> 
> What are the steps I should take to make sure that the 
> debugger stops at 
> breakpoints?  
> 
> Thank you in advance,
>    - CB
> 
> Jack Donohue wrote:
> 
> > When you set the breakpoint, does the line turn red? Or green?
> >
> > Christopher Mark Balz wrote:
> >
> >> I've been posting once every 10 days for weeks, and hope 
> someone can 
> >> point me in the right direction.
> >>
> >> Problem:
> >> -------
> >> Not able to get any use out of jdebug yet.
> >>
> >> With What:
> >> ---------
> >> Windows 2000 Service Pack 3, Java 1.4 SDK, Tomcat 3.3 
> Servlet Engine, 
> >> GNU Emacs 21.2.1, JDE 2.2.8, a web application that I'm trying to 
> >> debug, compiled with -g option, running Tomcat from 
> startup.bat with 
> >> normal successful operation, have TOMCAT_OPTS set to:
> >>     -Xdebug -Xnoagent 
> >> -Xrunjdwp:transport=dt_socket,address=6001,server=y,suspend=n
> >>
> >> Description:
> >> -----------
> >> I've gotten as far as successfully attaching to the Tomcat (v3.3) 
> >> Server process.  See below for output.  The web 
> application that I am 
> >> trying to debug does not seem to stop at the breakpoint I 
> set.  When 
> >> I try to Display->Variable, I get an obscure error message 
> referring 
> >> to an 'unbound slot'.
> >>
> >> Other Stuff that May Matter:
> >> ---------------------------
> >> On the JDE FAQ page, I noticed that it recommended 
> starting the web 
> >> server from the JDE.  Since tomcat.bat and tomcat.sh are a few 
> >> hundred lines long, I don't know if this is the best 
> option.  Is it 
> >> necessary?
> >>
> >> I found the simplified Tomcat startup commands in 
> startup.sh, created 
> >> a project file, and set the variables indicated in the FAQ entry.  
> >> But then on JDE->Run App, it used javaw (?I am not using 
> AWT) and the 
> >> -v option, which crashed the starting of the vm.  Any comments?
> >>
> >> Thank You in Advance!
> >> --------------------
> >>
> >> Debugger Output
> >> ---------------
> >>
> >> *** Debugger Output for Process 6001(1) ***
> >>
> >> Attached to process on port 6001 of local host.
> >> Attached VM (socket) Java Debug Interface (Reference 
> Implementation) 
> >> version 1.4
> >> Java Debug Wire Protocol (Reference Implementation) version 1.4
> >> JVM Debug Interface version 1.2
> >> JVM version 1.4.0 (Java HotSpot(TM) Client VM, mixed mode)
> >> Running 6001.
> >> Setting breakpoint at line 390 in QueryOutput.java.
> >> Resolved breakpoint set in QueryOutput.java at line 390.
> >> Cleared breakpoint at line 390 in file QueryOutput.java
> >> Setting breakpoint at line 390 in QueryOutput.java.
> >> Resolved breakpoint set in QueryOutput.java at line 390.
> >
> >
> 
> 
> -- 
> ". . . / This Cabinet is formd of Gold / And Pearl & Crystal 
> shining bright
> And within it opens into a World / . . .
> Another England there I saw / Another London with its Tower
> Another Thames & other Hills / And another pleasant Surrey Bower
> . . ."
> - from "The Crystal Cabinet", a poem by William Blake.
> 
> 

JDE 1.43: kill-line broken after upgrade

Hello,

I just upgraded my JDE to version 1.43 (via
the built-in stuff in the Options menu).
I am using XEmacs on RH 7.3, installed from
the RPM (xemacs-21.4.6-7).

After I upgraded I noticed that I can no
longer do C-k (kill-line).  The error
message that I get is:

    Wrong type argument: extentp, nil

I get the same error if I hit the DEL key or
if I try to kill a marked region with C-w.

Is this a known problem?
What should I do to fix this?  Is something
in the new JDE hogging these keys or
something similar?

Thanks,
Otis

________________________________________________
Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag

already installed...

Hi Artur,

I think I have already installed the jdee.

As I had uncompressed tar files on proper dirs, I hardcoded the paths on your 
script and it run to the end..

Any way, if tyou find the cause of errors on the scrip, please let me know..I 
think your script is extremely valuable to others to try to install jdee. I 
wonder if it could not be added on the jdee page...on a well visible corner 
spot. !! 

I have several questions about jdee ...

1 - It have templates to generate ejbs, servlets, beans, jsp.. and the rest of 
classes the j2ee include ?? Kinda jbuilder, Sun One Studio and other j2ee 
development tools ...

2 - Jdee is to be run on emacs, or xemacs ? 

Well, thanks for yor help.

Andrew

JDEbug breakpoint errors <- jde-db compile errors

Any attempt to set a JDEbug breakpoint produces the error:

Symbol`s function definition is void: line-beginning-position

I fixed this by deleting jdb-db.elc
Recompiling it produced these errors:

> While compiling jde-db-breakpoint-marker::initialize-instance:
>   ** attempt to inline line-beginning-position before it was defined
>   ** attempt to inline line-beginning-position before it was defined
>   ** attempt to inline line-beginning-position before it was defined
>   ** attempt to inline line-end-position before it was defined
>   ** attempt to inline line-beginning-position before it was defined
>   ** attempt to inline line-end-position before it was defined
> While compiling jde-db-debugger::jde-db-exec-next-cmd:
>   ** variable proc bound but not referenced
> While compiling jde-db-debugger::jde-db-debugger-start:
>   ** variable w32-quote-process-args bound but not referenced
>   ** variable win32-quote-process-args bound but not referenced
> While compiling jde-db-debugger::jde-db-debugger-launch:
>   ** variable working-directory bound but not referenced
>   ** variable source-directory bound but not referenced
> While compiling jde-db-debugger::jde-db-debugger-connect:
>   ** variable working-directory bound but not referenced
>   ** variable source-directory bound but not referenced
> While compiling the end of the data:
>   ** The following functions are not known to be defined: 
>     line-beginning-position, line-end-position, make-overlay,
>     overlay-put, overlay-get, delete-overlay, overlay-start

FYI, this is on cygwin xemacs 21.4.11, with all the latest packages from 
xemacs.org including JDE 2.3.2

There is is just one of many bugs I have hit, which I may or may not 
have time to investigate. Is there a more stable version of JDE available?

Jonathan