Java debugger?
Hello:
I'm having a frustrating problem in school. I am enrolled in a Java class, and we use an old version of JCreator LE. It has no debugger that I am aware of. I would like to install some sort of a debugger, but this presents a problem: since I don't have administrative priviledges, I doubt I caninstall a program, per se. I can otherwise copy and move files around easily; our school is not too tight on security.
Is there a debugger that does not require a formal installation with administrative priviledges? Preferrably a "visual" (graphical) one? (By necessity, I can subsist on a command line debugger just as well).
Thanks in advance for any help! This would alleviate a major burden for me!
[738 byte] By [
v0dKAa] at [2007-11-26 14:30:17]
Debug it on your own. I'm sure a high school Java course isn't giving you hard assignments.
Just use println statements added to the program to report what's happening and/or variable's values, that should suffice for most everything.
Judging from the nature of the replies, I feel it is necessary to note the following:
- I am not doing this to gain any sort of an unfair advantage in the course. I actually have some prior programming experience (in other languages), which led me to appreciate the value of a debugger. In no way can I see it as a "cheating" tool. The debugger is for convenience only.
- With regard to the difficulty of the assignments: more often than not, the cases where I wish to have a debugger most is when I stray from the assignment and try to do some experimenting on my own. The lack of a debugger stifles this experimentation.
- I mention again that the debugger is a tool of convenience. In lue of a debugger, one can, of course, insert a myriad of println() statements to accomplish the same end. Not only is it repetitive and annoying, but it also has no useful educational value whatsoever.
- I can see no viable objections that my teacher or school would have in my intentions. After all, the course is designed to give us experience in the development of software. This experience should, in my humble opinion, include using the debugger. After all, real programmers in the field do; so why shouldn't students, too?
- Finally, I intend to perform no harm to the school computer / network by installing the debugger. Even despite the fact that I'm asking for a way to bypass the school's security to install this debugger, it is merely a tool for my convenience, not an instrument of ill-willed destruction.
I'm sorry to get on the defensive side. I would just like to get some advice.
> Not only is it repetitive
> and annoying, but it also has no useful educational
> value whatsoever.
Yes it does. It teaches you to debug code on your own.
> - I can see no viable objections that my teacher or
> school would have in my intentions.
Other than trying to bypass their "security"? I almost got banned from the computers at my school for using a .bat file to try and compile my code (since the command prompt is blocked).
Apparently you are using Windows and they don't allow you to change the Registry, which just about every program that you install is going to do. The lack of any suggestions for debugger programs, and alternative solutions to the problem should be sending you a message.
The message I perceived you were sending is that I intended to use a debugger to gain some sort of an unfair advantage in the course, and thus you refused to help me. I can understand that. I issued my defense in my last post.
It's all right, though. I'll suffice on println() statements, as crude as I perceive them to be.
If anyone still has knowledge of some sort of a stand-alone executable program that can be used (perhaps without any need to perform an install process), then I'm still gladly accepting suggestions.
P.S.
>> Not only is it repetitive
>> and annoying, but it also has no useful educational
>> value whatsoever.
>
>Yes it does. It teaches you to debug code on your own.
I think I covered that quite thoroughly in my list of reasons. What use is there? The difference between "debugging on your own" and "using an external debugger" essentially comes down to whether it is you or another piece of software that puts a bunch of println() statements in the program. It is a matter of convenience. Correct me if you feel otherwise.
>> - I can see no viable objections that my teacher or
>> school would have in my intentions.
>
>Other than trying to bypass their "security"? I almost got banned from the >computers at my school for using a .bat file to try and compile my code >(since the command prompt is blocked).
Point taken. I'll ask my teacher if she would allow me to install software, or even use a debugger at all. Ideally, I would not bypass any security and use a debugger that does not require installation; but I would still ask my teacher.
I would ask your teacher. If that doesn't work, then just use println statements, there's nothing wrong with them. You could also install a debugger on your PC at home. I can't imagine you have that much free time during class.
