| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Michael Widenius | Date: | March 24 2001 8:44pm |
| Subject: | Re[31]: Warning: Got signal 14 from thread X | ||
| View as plain text | |||
Hi! >>>>> "Heikki" == Heikki Tuuri <Heikki.Tuuri@stripped> > writes: Heikki> Hi Sinisa, Monty, and Alex! Heikki> I am just compiling a debug version of Innobase. I will try to Heikki> run stress tests on our Sun. I see that also Monty is currently running Heikki> a test on our Sun. Heikki> But could you Alex describe, was it so that you were able to Heikki> get signal 14 even without running your 30 UPDATE daemon processes Heikki> on the database? Did you get it even if you restarted the server Heikki> and did not run any of these daemons? Heikki> When I try to run mysqld under gdb, it gets a SIGLWP from Heikki> __fdsync() at the start. With cont I get it to continue. Heikki> Does anyone know why it sends this signal? Try storing the following in a .gdbinit file in your current directory: set print sevenbit off handle SIGUSR1 nostop noprint handle SIGUSR2 nostop noprint handle SIGWAITING nostop noprint handle SIGLWP nostop noprint handle SIGPIPE nostop handle SIGALRM nostop handle SIGHUP nostop handle SIGTERM nostop noprint It should fix all the automatic signals you get from gdb. Note that MySQL needs SIGALRM to work; Are you modifying this in Innobase in any way? Regards, Monty
