public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: okay <szy_mailbox@126.com>
To: gcc-help@gcc.gnu.org
Subject: What's the possible reason of fclose core?
Date: Tue, 26 Apr 2022 22:45:28 +0800 (CST)	[thread overview]
Message-ID: <a284584.6179.18066559d53.Coremail.szy_mailbox@126.com> (raw)


#0  0x00007faad574d2a7 in raise () from /lib64/libc.so.6
#1  0x00007faad574e67a in abort () from /lib64/libc.so.6
#2  0x00007faad578c4f4 in __libc_message () from /lib64/libc.so.6
#3  0x00007faad5791966 in malloc_printerr () from /lib64/libc.so.6
#4  0x00007faad5791d02 in malloc_consolidate () from /lib64/libc.so.6
#5  0x00007faad5792753 in _int_free () from /lib64/libc.so.6
#6  0x00007faad5782bb9 in fclose@@GLIBC_2.2.5 () from /lib64/libc.so.6

 From the above core stack, because i can't see the parameter(file pointer, abbrv fp) value of fclose at frame 6, so fp  exists the following possible condition:
1) fp is NULL
2) fp is changed during running time
3) call fclose(fp)  twice continuously 
4) others reason haven't guessed.

  So i want to ask what's the possible condition can cause the above core? 
  Is it possible that other thread in same service change the fp value such as address violation operation?

  Thanks!

             reply	other threads:[~2022-04-26 14:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26 14:45 okay [this message]
2022-04-26 15:17 ` Xi Ruoyao
2022-04-27 12:44 ` Florian Weimer

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=a284584.6179.18066559d53.Coremail.szy_mailbox@126.com \
    --to=szy_mailbox@126.com \
    --cc=gcc-help@gcc.gnu.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).