JoeDog
commented
7 years ago Could you get a stack trace from the core dump?
gdb --core=/path/to/core bt
On Sat, Jan 21, 2017 at 3:50 AM, 有张纸 notifications@github.com wrote:
private BOOLEAN __lookup(HASH this, char key) { int x; NODE node;
if (key == NULL) { return FALSE; } x = __genkey(this->size, key); for (node = this->table[x]; node != NULL; node = node->next) { if (!strcmp(node->key, key)) { return TRUE; } } return FALSE; }
when i run siege -c 300 -t 1m -b xxx, it works well. when siege -c 500 -t 1m -b xxx, there is a core dump
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/JoeDog/siege/issues/95, or mute the thread https://github.com/notifications/unsubscribe-auth/AFMT5lnD9MXOH9eRkVvC3UGqmKxcfKzfks5rUcbtgaJpZM4LqAtY .
private BOOLEAN __lookup(HASH this, char key) { int x; NODE node;
if (key == NULL) { return FALSE; } x = __genkey(this->size, key); for (node = this->table[x]; node != NULL; node = node->next) { if (!strcmp(node->key, key)) { return TRUE; } } return FALSE; }
when i run siege -c 300 -t 1m -b xxx, it works well. when siege -c 500 -t 1m -b xxx, there is a core dump line " if (!strcmp(node->key, key)) {"