Hello Simon, I have the following line in my .gdbinit handle SIGUSR2 nostop noprint
I put this line when signals were used to flush a cash, and your experience shows that they are still used. Thanks. On 10/29/07, Simon Chow <[EMAIL PROTECTED]> wrote: > The gdb trace is like this below, and it seems happen when creating VM. > I am curious, Where do they come from and what is major task of them ? > BTW. Can I block these signal when debugging VM? > > Starting program: > /workspace/Harmony/trunk/working_vm/build/deploy/jdk/jre/bin/java Hello > [Thread debugging using libthread_db enabled] > [New Thread -1212938544 (LWP 5736)] > [New Thread -1214088304 (LWP 5739)] > [New Thread -1508099184 (LWP 5740)] > [New Thread -1511539824 (LWP 5741)] > [New Thread -1512068208 (LWP 5744)] > > Program received signal SIGUSR2, User defined signal 2. > [Switching to Thread -1212938544 (LWP 5736)] > 0xffffe410 in __kernel_vsyscall () > (gdb) c > Continuing. > > Program received signal SIGUSR2, User defined signal 2. > 0xffffe410 in __kernel_vsyscall () > (gdb) c > Continuing. > [New Thread -1512596592 (LWP 5746)] > > Program received signal SIGUSR2, User defined signal 2. > 0xffffe410 in __kernel_vsyscall () > (gdb) c > Breakpoint 1, main_runJavaMain (env=0x8429b98, mainClassName=0xbfc89bc8 > "Hello", nameIsUTF=0, java_argc=0, > java_argv=0xbfc8970c, portLibrary=0xbfc89298) at ../shared/main.c:1322 > 1322 (*env)->DeleteLocalRef (env, stringClass); > > > > -- > From : [EMAIL PROTECTED] School of Fudan University > -- With best regards, Alexei, ESSD, Intel
