public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "werner at suse dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug string/29327] A SIGSEGV in hardware optimized memset for sse2 __memset_sse2_unaligned_erms()
Date: Mon, 25 Jul 2022 14:20:24 +0000	[thread overview]
Message-ID: <bug-29327-131-q7hMUOs77Q@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29327-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29327

--- Comment #32 from Dr. Werner Fink <werner at suse dot de> ---
For me it looks like a problem with (lib)sqlite3 and its memory managment and
libmemusage.so

35108
35109     if( new_ht==0 ) return 0;
35110     sqlite3_free(pH->ht);
35111     pH->ht = new_ht;
35112     pH->htsize = new_size = sqlite3MallocSize(new_ht)/sizeof(struct _ht);
35113     memset(new_ht, 0, new_size*sizeof(struct _ht));
35114     for(elem=pH->first, pH->first=0; elem; elem = next_elem){
35115       unsigned int h = strHash(elem->pKey) % new_size;
35116       next_elem = elem->next;
35117       insertElement(pH, &new_ht[h], elem);
(gdb) print new_ht
$8 = (struct _ht *) 0x1ba9330
(gdb) print *new_ht
$9 = {count = 0, chain = 0x0}
(gdb) print new_size
$10 = 4293843945
(gdb) print pH->htsize
$11 = 0

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-07-25 14:20 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07 11:54 [Bug libc/29327] New: " werner at suse dot de
2022-07-07 11:55 ` [Bug libc/29327] " werner at suse dot de
2022-07-07 11:56 ` werner at suse dot de
2022-07-07 12:07 ` werner at suse dot de
2022-07-07 17:50 ` [Bug string/29327] " fweimer at redhat dot com
2022-07-07 18:24 ` goldstein.w.n at gmail dot com
2022-07-07 18:52 ` goldstein.w.n at gmail dot com
2022-07-07 19:26 ` goldstein.w.n at gmail dot com
2022-07-07 20:03 ` hjl.tools at gmail dot com
2022-07-07 20:10 ` goldstein.w.n at gmail dot com
2022-07-08 12:03 ` werner at suse dot de
2022-07-08 12:26 ` werner at suse dot de
2022-07-08 12:29 ` werner at suse dot de
2022-07-08 14:29 ` hjl.tools at gmail dot com
2022-07-08 15:50 ` goldstein.w.n at gmail dot com
2022-07-11  8:15 ` werner at suse dot de
2022-07-11  8:23 ` werner at suse dot de
2022-07-11 14:10 ` hjl.tools at gmail dot com
2022-07-12  7:02 ` werner at suse dot de
2022-07-12  7:12 ` werner at suse dot de
2022-07-12  7:20 ` werner at suse dot de
2022-07-12 14:47 ` hjl.tools at gmail dot com
2022-07-12 15:46 ` hjl.tools at gmail dot com
2022-07-13  9:22 ` werner at suse dot de
2022-07-13 14:30 ` hjl.tools at gmail dot com
2022-07-13 15:47 ` goldstein.w.n at gmail dot com
2022-07-14  7:36 ` werner at suse dot de
2022-07-14 15:42 ` hjl.tools at gmail dot com
2022-07-19  9:58 ` werner at suse dot de
2022-07-19 17:47 ` hjl.tools at gmail dot com
2022-07-22 11:04 ` werner at suse dot de
2022-07-22 11:13 ` werner at suse dot de
2022-07-22 14:26 ` goldstein.w.n at gmail dot com
2022-07-25  6:00 ` werner at suse dot de
2022-07-25 14:20 ` werner at suse dot de [this message]
2022-07-28 11:44 ` bww9643 at gmail dot com
2022-07-28 11:46 ` bww9643 at gmail dot com
2022-08-09 12:46 ` werner at suse dot de

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-29327-131-q7hMUOs77Q@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).