Hi Zack,
Which debugger you used? jdb?
What commands did you run in order to make it work?
Could you write short notice for other people how
to run a debugger?
Jacob
Zack Grossbart wrote:
>
> Nathan,
>
> Thank you very much for your help. I now have a working debugger on Linux.
> I have only one remaining issue. If you must pass in the bootclasspath, is
> there anyway to only concatenate it? I'm thinking specifically about
> i18n.jar. This JAR is needed for internationalization support.
>
> I can build a bootclasspath with only the stuff I need in it, but I would
> like to be able to assure that the bootclasspath that is set, and could have
> been set by the user, is used.
>
> Thanks a lot.
>
> Zack
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> > Nathan Meyers
> > Sent: Wednesday, April 19, 2000 12:16 PM
> > To: Zack Grossbart
> > Cc: noisebrain; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> > Subject: Re: jdb tips?
> >
> >
> > Zack Grossbart wrote:
> > >
> > > Nathan,
> > >
> > > Thank you very much for your help. I need to pass a
> > couple more flags than
> > > just -debug. When I launch:
> > >
> > > java -Djava.compiler=NONE -debug
> > -Xbootclasspath:/path/to/my/jdk/jre/lib/rt.
> > > jar:/path/to/my/jdk/lib/tools.jar
> > -Xrunjdwp:transport=dt_shmem,address=agfrn
> > > ,server=y,suspend=n myClass
> > >
> >
> > Followup to my previous response...
> >
> > I overlooked one thing when I tried your example... I run with green
> > threads by default. It appears that jpda fails with native threads in
> > Blackdown RC4. Try running "java -green ..." or setting the THREADS_FLAG
> > environment variable to "green".
> >
> > Nathan
> >
> >
> >
> > > my JVM crashes with the following trace:
> > >
> > > Agent password=5i442a
> > > Transport dt_shmem failed to initialize, rc = 509.
> > > FATAL ERROR in native method: No transports initialized
> > > SIGABRT 6* abort (generated by abort(3) routine, also SIGIOT)
> > > si_signo [6]: SIGABRT 6* abort (generated by abort(3)
> > routine, also
> > > SIGIOT)
> > > si_errno [0]: Success
> > > si_code [0]: SI_USER [pid: 0, uid: 0]
> > > stackpointer=0xbfffeb0c
> > >
> > > Full thread dump Classic VM (Linux_JDK_1.2.2_RC4, native threads):
> > > "Debugger agent" (TID:0x40e9e640, sys_thread_t:0x80f8df8, state:R,
> > > native ID:0x1005) prio=10
> > > "Finalizer" (TID:0x40e98320, sys_thread_t:0x80d4c10,
> > state:CW, native
> > > ID:0xc04) prio=8
> > > at java.lang.Object.wait(Native Method)
> > > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:112)
> > > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
> > > at
> > java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:174)
> > > "Reference Handler" (TID:0x40e983b0,
> > sys_thread_t:0x80cec78, state:CW,
> > > native ID:0x803) prio=10
> > > at java.lang.Object.wait(Native Method)
> > > at java.lang.Object.wait(Object.java:424)
> > > at
> > java.lang.ref.Reference$ReferenceHandler.run(Reference.java:114)
> > > "SIGQUIT handler" (TID:0x40e983e0, sys_thread_t:0x80ce8e8, state:R,
> > > native ID:0x402) prio=5
> > > "main" (TID:0x40e981e0, sys_thread_t:0x80537a8, state:R, native
> > > ID:0x400) prio=5
> > > Monitor Cache Dump:
> > > java.lang.ref.ReferenceQueue$Lock@40E98338/40ECE028: <unowned>
> > > Waiting to be notified:
> > > "Finalizer" (0x80d4c10)
> > > java.lang.ref.Reference$Lock@40E983C0/40ECDB20: <unowned>
> > > Waiting to be notified:
> > > "Reference Handler" (0x80cec78)
> > > Registered Monitor Dump:
> > > JDWP Transport Send Monitor: <unowned>
> > > JDWP Transport Listener Monitor: <unowned>
> > > JDWP Initialization Monitor: <unowned>
> > > JDWP Invocation Lock: <unowned>
> > > JDWP Step Handler Lock: <unowned>
> > > JDWP Thread Lock: <unowned>
> > > JDWP Reference Table Monitor: <unowned>
> > > JDWP Alloc Lock: <unowned>
> > > utf8 hash table: <unowned>
> > > JNI pinning lock: <unowned>
> > > JNI global reference lock: <unowned>
> > > BinClass lock: <unowned>
> > > Class linking lock: <unowned>
> > > System class loader lock: <unowned>
> > > Code rewrite lock: <unowned>
> > > Heap lock: <unowned>
> > > Monitor cache lock: owner "main" (0x80537a8) 1 entry
> > > Thread queue lock: owner "main" (0x80537a8) 1 entry
> > > Monitor registry: owner "main" (0x80537a8) 1 entry
> > >
> > > Thanks a lot for your help.
> > >
> > > Zack
> > >
> > > P.S. I am running glibc 2.1.2.
> > >
> > > > -----Original Message-----
> > > > From: nathanm [mailto:nathanm]On Behalf Of Nathan Meyers
> > > > Sent: Wednesday, April 19, 2000 10:38 AM
> > > > To: Zack Grossbart
> > > > Cc: noisebrain; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> > > > Subject: Re: jdb tips?
> > > >
> > > >
> > > > Zack Grossbart wrote:
> > > > >
> > > > > Nathan,
> > > > >
> > > > > When I try to launch a JVM with the debug options it
> > > > says there is no JDWP
> > > > > implementation available, and I can not find the JPDA or the
> > > > JVMDI shared
> > > > > libraries in my JDK. I am using Blackdown RC-4. Do you know
> > > > if there is
> > > > > anything that needs to be installed on top of the JDK?
> > > >
> > > > You just run "java -debug" and see a message mentioning JDWP by name?
> > > > I've never managed to see that one, and I have successfully used
> > > > debuggers that require JPDA (like JBuilder's) with Blackdown RC4. Very
> > > > strange.
> > > >
> > > > The only requirements I have noticed for the debug option are that the
> > > > tools jarfile be added to the boot classpath, and that JIT be
> > disabled:
> > > >
> > > > > java -Djava.compiler=
> > > > -Xbootclasspath:/path/to/jdk/jre/lib/rt.jar:/path/to/jdk/lib/tools
> > > > .jar -debug ...
> > > >
> > > > If you don't get an "agent password" message, I'd guess that
> > something's
> > > > broken with your installation. Just to hit the obvious case: you are
> > > > running in a glibc 2.1.2 environment, right?
> > > >
> > > > Nathan
> > > >
> > > >
> > > > >
> > > > > Thanks
> > > > > Zack
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Nathan Meyers [mailto:[EMAIL PROTECTED]]
> > > > > > Sent: Tuesday, April 18, 2000 7:20 PM
> > > > > > To: Zack Grossbart; noisebrain; [EMAIL PROTECTED]
> > > > > > Cc: [EMAIL PROTECTED]
> > > > > > Subject: Re: jdb tips?
> > > > > >
> > > > > >
> > > > > > On Tue, Apr 18, 2000 at 02:06:39PM -0400, Zack Grossbart wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > I don't think there is a full JPDA or JVMDI implementation
> > > > > > on Linux. This
> > > > > > > means that you can act as a JDPA client from Linux (i.e.
> > > > debug a virtual
> > > > > > > machine on windows from Linux), but you can not do it the other
> > > > > > way around.
> > > > > > > This includes using JDB against an application running on Linux.
> > > > > > >
> > > > > > > Sorry for the bad news. I'd be very happy if I was
> > contradicted.
> > > > > >
> > > > > > Then you can cheer up :-). The Sun/Inprise JDK has it, and
> > > > the Blackdown
> > > > > > JDK has had it since the current release candidate came out.
> > > > The problem
> > > > > > here appears to be a lack of current jdb documentation.
> > > > > >
> > > > > > The good news is, with JPDA, you can use debugger clients
> > > > like those in
> > > > > > JBuilder, so you're not stuck with jdb and its
> > undocumented options.
> > > > > >
> > > > > > Nathan
> > > > > >
> > > > > > >
> > > > > > > Zack
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: noisebrain [mailto:[EMAIL PROTECTED]]
> > > > > > > > Sent: Thursday, April 13, 2000 10:42 PM
> > > > > > > > To: [EMAIL PROTECTED]
> > > > > > > > Cc: [EMAIL PROTECTED]
> > > > > > > > Subject: jdb tips?
> > > > > > > >
> > > > > > > >
> > > > > > > > Hello,
> > > > > > > >
> > > > > > > > i'm trying jdb for the first time and am having difficulties.
> > > > > > > >
> > > > > > > > Using sun/inprise/blackdown 1.2.2(feb version) I run
> > my app with
> > > > > > > > -Xdebug -Djava.compiler=NONE -Xbootclasspath:...
> > > > > > > > and it prints out e.g.
> > > > > > > > Agent password=3i5347
> > > > > > > >
> > > > > > > > The jdb tool doc says that I can then run
> > > > > > > > jdb -host <host> -password <password>
> > > > > > > > but jdb itself says it does not recognize -host. Jdb's
> > > > usage message
> > > > > > > > says it recognizes
> > > > > > > > -connect <connector-name>:<name1>=<value1>,.
> > > > > > > > or
> > > > > > > > -attach <address>
> > > > > > > > but the html doc doesn't describe what <address> or
> > > > > > <connector-name> are.
> > > > > > > >
> > > > > > > > Thanks for any help
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > ----------------------------------------------------------------------
> > > > > > > > To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> > > > > > > > with a subject of "unsubscribe". Trouble? Contact
> > > > [EMAIL PROTECTED]
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > ----------------------------------------------------------------------
> > > > > > > To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> > > > > > > with a subject of "unsubscribe". Trouble? Contact
> > [EMAIL PROTECTED]
> > > > > >
> > > > > >
> > > > > >
> > ----------------------------------------------------------------------
> > > > > > To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> > > > > > with a subject of "unsubscribe". Trouble? Contact
> > [EMAIL PROTECTED]
> > > > > >
> >
> >
> > ----------------------------------------------------------------------
> > To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> >
>
> ----------------------------------------------------------------------
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
