public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mehmetgelisin at aol dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/26828] SIGSEGV in follow_die_offset dwarf2/read.c:22950
Date: Fri, 10 Sep 2021 19:39:06 +0000	[thread overview]
Message-ID: <bug-26828-4717-d6spfeokzV@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26828-4717@http.sourceware.org/bugzilla/>

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

Mehmet gelisin <mehmetgelisin at aol dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mehmetgelisin at aol dot com

--- Comment #36 from Mehmet gelisin <mehmetgelisin at aol dot com> ---
ssibly similar to 23220 however on 64-bit recent Debian sid with
trivial code I see :  http://www-look-4.com/

mimas$ 
mimas$ uname -a  http://www.compilatori.com/
Linux mimas 5.10.0-6-sparc64 #1 Debian 5.10.28-1 (2021-04-09) sparc64 GNU/Linux
mimas$ 
 http://www.wearelondonmade.com/
mimas$ 
mimas$ /usr/bin/gcc --version 
gcc (Debian 10.2.1-6) 10.2.1 20210110 http://www.jopspeech.com/
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
http://joerg.li/ 

mimas$ 

mimas$ http://connstr.net/ 
mimas$ cat -n foo.c 
     1
     2  #include <stdio.h>
     3  #include <stdlib.h>
     4 http://embermanchester.uk/ 
     5  int main(int argc, char **argv)
     6  {
     7      int a = 1;
     8 http://www.slipstone.co.uk/ 
     9      printf("a = %i\n", a);
    10
    11      printf("&a = %p\n", &a);
    12
    13      return EXIT_SUCCESS;
    14 http://www.logoarts.co.uk/ 
    15  }
    16
mimas$ 

mimas$  http://www.acpirateradio.co.uk/ 
mimas$ /usr/bin/gcc -std=iso9899:1999 -pedantic -pedantic-errors -fno-builtin
-g -m64 -O0 -mno-app-regs -mcpu=ultrasparc -mmemory-model=tso -o foo foo.c 
https://waytowhatsnext.com/ 
mimas$  debugging a core file with "-i=mi" and repeatedly running e.g.
"-stack-list-variables --thread 1 --frame 0 --simple-values" results in a
segmentation fault. https://www.webb-dev.co.uk/ 

The first call returns "frame" and "variables" information.
The second call returns just the "variables".
The third call segfaults in "follow_die_offset" (dwarf
http://www.iu-bloomington.com/

The first call returns "frame" and "variables" information.
The second call returns just the "variables".
The third call segfaults in "follow_die_offset" (dwarf2/read.c:22950).

The segfaulting line reads:
   target_cu->ancestor = cu; https://komiya-dental.com/

target_cu is apparent

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

  parent reply	other threads:[~2021-09-10 19:39 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 10:42 [Bug gdb/26828] New: " nilsgladitz at gmail dot com
2020-11-02 13:25 ` [Bug gdb/26828] " simark at simark dot ca
2020-11-02 15:21 ` nilsgladitz at gmail dot com
2020-11-02 15:36 ` simark at simark dot ca
2020-11-03 11:36 ` nilsgladitz at gmail dot com
2020-11-03 13:37 ` simark at simark dot ca
2020-11-03 14:03 ` simark at simark dot ca
2020-11-03 14:32 ` simark at simark dot ca
2020-11-03 15:02 ` nilsgladitz at gmail dot com
2020-11-03 17:05 ` simark at simark dot ca
2020-11-03 19:45 ` nilsgladitz at gmail dot com
2020-11-03 19:52 ` simark at simark dot ca
2020-11-03 20:14 ` nilsgladitz at gmail dot com
2020-11-03 20:52 ` simark at simark dot ca
2020-11-04  7:43 ` nilsgladitz at gmail dot com
2020-11-04 16:53 ` simark at simark dot ca
2020-11-08 16:16 ` nilsgladitz at gmail dot com
2020-11-08 16:17 ` nilsgladitz at gmail dot com
2020-11-08 16:45 ` simark at simark dot ca
2020-11-10 14:15 ` simark at simark dot ca
2020-11-13 17:03 ` cvs-commit at gcc dot gnu.org
2020-11-13 17:22 ` simark at simark dot ca
2020-11-13 18:13 ` nilsgladitz at gmail dot com
2020-11-16 18:21 ` simark at simark dot ca
2020-11-17 19:13 ` simark at simark dot ca
2021-01-21  2:05 ` cvs-commit at gcc dot gnu.org
2021-02-20 19:35 ` ReD at idp dot it
2021-02-20 20:40 ` simark at simark dot ca
2021-02-23 18:39 ` cvs-commit at gcc dot gnu.org
2021-02-23 18:39 ` cvs-commit at gcc dot gnu.org
2021-02-23 23:32 ` cvs-commit at gcc dot gnu.org
2021-02-23 23:32 ` cvs-commit at gcc dot gnu.org
2021-02-23 23:32 ` simark at simark dot ca
2021-06-27 17:58 ` ahmedsayeed1982 at yahoo dot com
2021-08-10 12:45 ` ucelsanicin at yahoo dot com
2021-09-02 11:06 ` donipah907 at mtlcz dot com
2021-09-02 11:17 ` mark at klomp dot org
2021-09-06  9:08 ` focixujo at livinginsurance dot co.uk
2021-09-10 19:39 ` mehmetgelisin at aol dot com [this message]
2021-09-22 10:19 ` diheto5497 at secbuf dot com
2021-09-22 13:58 ` ReD at idp dot it
2021-09-28  1:20 ` crownfamilydentistry at hotmail dot com
2021-10-09 11:00 ` gulsenenginar at aol dot com
2021-10-17 19:48 ` vmireskazki at gmail dot com
2021-10-19  7:15 ` progonsaytu at gmail dot com
2021-10-24 10:03 ` glassmtech at ukr dot net
2021-11-24 13:44 ` allen at rockvalleymarketing dot com

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-26828-4717-d6spfeokzV@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).