public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
@ 2021-01-04 12:57 koachan+sourceware at protonmail dot com
  2021-01-04 15:58 ` [Bug backtrace/27147] " simark at simark dot ca
                   ` (39 more replies)
  0 siblings, 40 replies; 41+ messages in thread
From: koachan+sourceware at protonmail dot com @ 2021-01-04 12:57 UTC (permalink / raw)
  To: gdb-prs

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

            Bug ID: 27147
           Summary: [GNU/Linux, sparc64] GDB is unable to print full stack
                    trace (got "previous frame inner to this frame"
                    errors)
           Product: gdb
           Version: HEAD
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: backtrace
          Assignee: unassigned at sourceware dot org
          Reporter: koachan+sourceware at protonmail dot com
  Target Milestone: ---

Created attachment 13091
  --> https://sourceware.org/bugzilla/attachment.cgi?id=13091&action=edit
Test code to trigger the behavior

On sparc64, GDB 10.1 seems to corrupt stack traces. It displays the topmost
two functions just fine, but everything beyond that seems to be corrupted.

Steps to reproduce:

- Compile the attached gdb-test.c on sparc64.
- Load the binary under GDB, set breakpoint on puts.
- Run it, and when it reaches the breakpoint, print a backtrace.

Expected result (from GDB 9.2):
#0  0x0000000000108de4 in puts ()
#1  0x0000000000100950 in hello () at gdb-test.c:4
#2  0x0000000000100968 in main () at gdb-test.c:8

Actual result (from GDB latest git):
#0  0x0000000000108de4 in puts ()
#1  0x0000000000100950 in hello () at gdb-test.c:4
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Worked fine on 9.2, started experiencing problem in 10.1, and it seems that
latest git version (11.0.50.20210104-git, commit
e9cf3691bfa140469d52815a2307b00eecf7917c)
is still problematic.

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
@ 2021-01-04 15:58 ` simark at simark dot ca
  2021-01-04 16:26 ` simark at simark dot ca
                   ` (38 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: simark at simark dot ca @ 2021-01-04 15:58 UTC (permalink / raw)
  To: gdb-prs

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

Simon Marchi <simark at simark dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |simark at simark dot ca

--- Comment #1 from Simon Marchi <simark at simark dot ca> ---
Would you be able to provide a compiled binary and core dump that reproduce
this?  This would give us a chance to investigate the issue on a non-sparc
computer.

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
  2021-01-04 15:58 ` [Bug backtrace/27147] " simark at simark dot ca
@ 2021-01-04 16:26 ` simark at simark dot ca
  2021-01-04 18:58 ` simark at simark dot ca
                   ` (37 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: simark at simark dot ca @ 2021-01-04 16:26 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #2 from Simon Marchi <simark at simark dot ca> ---
Can you also tell how you compiled the binary, which compiler and which command
line?

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
  2021-01-04 15:58 ` [Bug backtrace/27147] " simark at simark dot ca
  2021-01-04 16:26 ` simark at simark dot ca
@ 2021-01-04 18:58 ` simark at simark dot ca
  2021-01-04 23:41 ` koachan+sourceware at protonmail dot com
                   ` (36 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: simark at simark dot ca @ 2021-01-04 18:58 UTC (permalink / raw)
  To: gdb-prs

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

Simon Marchi <simark at simark dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2021-01-04
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
   Target Milestone|---                         |10.2

--- Comment #3 from Simon Marchi <simark at simark dot ca> ---
Ok, I was able to reproduce this on gcc102, on the gcc compile farm.  It
bisected to 5b6d1e4fa4fc ("Multi-target support").

At 5b6d1e4fa4fc:

$ ./binutils-gdb/gdb/gdb --data-directory binutils-gdb/gdb/data-directory
-batch a.out -ex "b puts" -ex "r" -ex "bt"
Breakpoint 1 at 0x1021a0

Breakpoint 1, 0xffff80010019c63c in puts () from
/lib/sparc64-linux-gnu/libc.so.6
#0  0xffff80010019c63c in puts () from /lib/sparc64-linux-gnu/libc.so.6
#1  0x000007feffdee2d9 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

At 5b6d1e4fa4fc^:

./binutils-gdb/gdb/gdb --data-directory binutils-gdb/gdb/data-directory -batch
a.out -ex "b puts" -ex "r" -ex "bt"
Breakpoint 1 at 0x1021a0

Breakpoint 1, 0xffff80010019c63c in puts () from
/lib/sparc64-linux-gnu/libc.so.6
#0  0xffff80010019c63c in puts () from /lib/sparc64-linux-gnu/libc.so.6
#1  0x00000100000007f8 in hello () at test.c:4
#2  0x0000010000000810 in main () at test.c:8

Since this is a 9 -> 10 regression, I'll mark it with the 10.2 milestone.  I
don't plan to look more into it at the moment.

Note: I tried to generate a core file, to be able to analyze further on my
local machine, but I wasn't able to load it.  GDB doesn't find the registers in
the core file:

  warning: Couldn't find general-purpose registers in core file.

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (2 preceding siblings ...)
  2021-01-04 18:58 ` simark at simark dot ca
@ 2021-01-04 23:41 ` koachan+sourceware at protonmail dot com
  2021-01-04 23:42 ` koachan+sourceware at protonmail dot com
                   ` (35 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: koachan+sourceware at protonmail dot com @ 2021-01-04 23:41 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #4 from Koakuma <koachan+sourceware at protonmail dot com> ---
Created attachment 13093
  --> https://sourceware.org/bugzilla/attachment.cgi?id=13093&action=edit
Statically-compiled binary of the test case, made with GCC 9.3.0

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (3 preceding siblings ...)
  2021-01-04 23:41 ` koachan+sourceware at protonmail dot com
@ 2021-01-04 23:42 ` koachan+sourceware at protonmail dot com
  2021-02-18 17:35 ` simark at simark dot ca
                   ` (34 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: koachan+sourceware at protonmail dot com @ 2021-01-04 23:42 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #5 from Koakuma <koachan+sourceware at protonmail dot com> ---
(In reply to Simon Marchi from comment #1)
> Would you be able to provide a compiled binary and core dump that reproduce
> this?  This would give us a chance to investigate the issue on a non-sparc
> computer.

Sorry for the late reply, I've attached a binary made with GCC 9.3.0. It should
be
easily testable under qemu-sparc64 or other emulators since it's
statically-linked.
It was built with a `cc -static -g -o gdb-test gdb-test.c`.

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (4 preceding siblings ...)
  2021-01-04 23:42 ` koachan+sourceware at protonmail dot com
@ 2021-02-18 17:35 ` simark at simark dot ca
  2021-02-23 17:48 ` andrew.burgess at embecosm dot com
                   ` (33 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: simark at simark dot ca @ 2021-02-18 17:35 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #6 from Simon Marchi <simark at simark dot ca> ---
I compared a good and bad execution, and it seems it starts to diverge when we
try to find an unwinder for frame 0.  So the line just before this one (the
backtrace is taken at the last working commit, so the parent of the
multi-target commit):

#0  compute_frame_id (fi=0x10007c50040) at
/home/simark/src/wt/good/gdb/frame.c:549
#1  0x000001000324ddd8 in get_prev_frame_if_no_cycle (this_frame=0x10007c4f230)
at /home/simark/src/wt/good/gdb/frame.c:1927
#2  0x000001000324f9f8 in get_prev_frame_always_1 (this_frame=0x10007c4f230) at
/home/simark/src/wt/good/gdb/frame.c:2108
#3  0x000001000324fa38 in get_prev_frame_always (this_frame=0x10007c4f230) at
/home/simark/src/wt/good/gdb/frame.c:2124
#4  0x00000100032511fc in get_prev_frame (this_frame=0x10007c4f230) at
/home/simark/src/wt/good/gdb/frame.c:2376
#5  0x00000100042972c0 in backtrace_command_1 (fp_opts=..., bt_opts=...,
count_exp=0x0, from_tty=1) at /home/simark/src/wt/good/gdb/stack.c:2055
#6  0x0000010004297918 in backtrace_command (arg=0x0, from_tty=1) at
/home/simark/src/wt/good/gdb/stack.c:2183
#7  0x0000010002a4a538 in do_const_cfunc (c=0x10007c93390, args=0x0,
from_tty=1) at /home/simark/src/wt/good/gdb/cli/cli-decode.c:107
#8  0x0000010002a56ea4 in cmd_func (cmd=0x10007c93390, args=0x0, from_tty=1) at
/home/simark/src/wt/good/gdb/cli/cli-decode.c:1952
#9  0x00000100045e32e4 in execute_command (p=0x10007ab9c52 "", from_tty=1) at
/home/simark/src/wt/good/gdb/top.c:653
#10 0x00000100031b21c0 in command_handler (command=0x10007ab9c50 "bt") at
/home/simark/src/wt/good/gdb/event-top.c:587
#11 0x00000100031b2d4c in command_line_handler (rl=...) at
/home/simark/src/wt/good/gdb/event-top.c:772
#12 0x00000100031b06e4 in gdb_rl_callback_handler (rl=0x10007cc5e30 "bt") at
/home/simark/src/wt/good/gdb/event-top.c:218
#13 0x0000010004ae6410 in rl_callback_read_char () at
/home/simark/src/wt/good/readline/readline/callback.c:281
#14 0x00000100031b02b0 in gdb_rl_callback_read_char_wrapper_noexcept () at
/home/simark/src/wt/good/gdb/event-top.c:176
#15 0x00000100031b03d4 in gdb_rl_callback_read_char_wrapper
(client_data=0x10007ab99c0) at /home/simark/src/wt/good/gdb/event-top.c:193
#16 0x00000100031b1a4c in stdin_event_handler (error=0,
client_data=0x10007ab99c0) at /home/simark/src/wt/good/gdb/event-top.c:515
#17 0x00000100031aa778 in handle_file_event (file_ptr=0x10007d6aa20,
ready_mask=1) at /home/simark/src/wt/good/gdb/event-loop.c:731
#18 0x00000100031ab3e0 in gdb_wait_for_event (block=1) at
/home/simark/src/wt/good/gdb/event-loop.c:857
#19 0x00000100031a63f4 in gdb_do_one_event () at
/home/simark/src/wt/good/gdb/event-loop.c:346
#20 0x00000100031a6450 in start_event_loop () at
/home/simark/src/wt/good/gdb/event-loop.c:370
#21 0x0000010003877188 in captured_command_loop () at
/home/simark/src/wt/good/gdb/main.c:360
#22 0x000001000387ad3c in captured_main (data=0x7fefffff0e8) at
/home/simark/src/wt/good/gdb/main.c:1203
#23 0x000001000387ae60 in gdb_main (args=0x7fefffff0e8) at
/home/simark/src/wt/good/gdb/main.c:1218
#24 0x000001000227bbf4 in main (argc=8, argv=0x7fefffff4a8) at
/home/simark/src/wt/good/gdb/gdb.c:32

At this point, in the good:

(gdb) p fi.unwind 
$11 = (const frame_unwind *) 0x10005bd2470 <dwarf2_frame_unwind>

In the bad:

(gdb) p fi.unwind 
$4 = (const frame_unwind *) 0x10006367800 <sparc64_frame_unwind>

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (5 preceding siblings ...)
  2021-02-18 17:35 ` simark at simark dot ca
@ 2021-02-23 17:48 ` andrew.burgess at embecosm dot com
  2021-02-23 18:23 ` andrew.burgess at embecosm dot com
                   ` (32 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: andrew.burgess at embecosm dot com @ 2021-02-23 17:48 UTC (permalink / raw)
  To: gdb-prs

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

Andrew Burgess <andrew.burgess at embecosm dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |andrew.burgess at embecosm dot com

--- Comment #7 from Andrew Burgess <andrew.burgess at embecosm dot com> ---
I took a look at this bug and tracked down what I think caused the regression.

If you apply this patch to GDB:

diff --git a/gdb/sparc-tdep.c b/gdb/sparc-tdep.c
index 4f9c679b55c..4da94e8e0bb 100644
--- a/gdb/sparc-tdep.c
+++ b/gdb/sparc-tdep.c
@@ -1957,7 +1957,9 @@ sparc_supply_rwindow (struct regcache *regcache,
CORE_ADDR sp, int regnum)
        {
          if (regnum == i || regnum == -1)
            {
-             target_read_memory (sp + ((i - SPARC_L0_REGNUM) * 8), buf, 8);
+             if (target_read_memory (sp + ((i - SPARC_L0_REGNUM) * 8), buf, 8)
== -1)
+               error (_("failed to read target memory at %s"),
+                      core_addr_to_string (sp + ((i - SPARC_L0_REGNUM) * 8)));

              /* Handle StackGhost.  */
              if (i == SPARC_I7_REGNUM)

Then you should find that on commit 75c6c844d9d everything is fine, but on
commit 5b6d1e4fa4f you'll start seeing error.  The reason is that inferior_ptid
is set to something valid in the working commit, but is now null_ptid in the
broken commit.

As an experiment I tried hacking things so that if we get into
sparc_supply_rwindow and inferior_ptid is null_ptid then we find a "suitable"
value and set it, and this does indeed resolve the issue.

Right now I'm trying to figure out the correct way that inferior_ptid should be
getting set at this point.

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (6 preceding siblings ...)
  2021-02-23 17:48 ` andrew.burgess at embecosm dot com
@ 2021-02-23 18:23 ` andrew.burgess at embecosm dot com
  2021-02-23 18:32 ` simark at simark dot ca
                   ` (31 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: andrew.burgess at embecosm dot com @ 2021-02-23 18:23 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #8 from Andrew Burgess <andrew.burgess at embecosm dot com> ---
I'm testing this possible patch:

diff --git a/gdb/sparc-tdep.c b/gdb/sparc-tdep.c
index 4f9c679b55c..6f6157fc461 100644
--- a/gdb/sparc-tdep.c
+++ b/gdb/sparc-tdep.c
@@ -1948,6 +1948,11 @@ sparc_supply_rwindow (struct regcache *regcache,
CORE_ADDR sp, int regnum)
   gdb_byte buf[8];
   int i;

+  /* Ensure the correct inferior_ptid is in place before calling target
+     methods.  */
+  scoped_restore save_inferior_ptid = make_scoped_restore (&inferior_ptid);
+  inferior_ptid = regcache->ptid ();
+
   if (sp & 1)
     {
       /* Registers are 64-bit.  */

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (7 preceding siblings ...)
  2021-02-23 18:23 ` andrew.burgess at embecosm dot com
@ 2021-02-23 18:32 ` simark at simark dot ca
  2021-02-23 18:33 ` simark at simark dot ca
                   ` (30 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: simark at simark dot ca @ 2021-02-23 18:32 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #9 from Simon Marchi <simark at simark dot ca> ---
(In reply to Andrew Burgess from comment #7)
> I took a look at this bug and tracked down what I think caused the
> regression.
> 
> If you apply this patch to GDB:
> 
> diff --git a/gdb/sparc-tdep.c b/gdb/sparc-tdep.c
> index 4f9c679b55c..4da94e8e0bb 100644
> --- a/gdb/sparc-tdep.c
> +++ b/gdb/sparc-tdep.c
> @@ -1957,7 +1957,9 @@ sparc_supply_rwindow (struct regcache *regcache,
> CORE_ADDR sp, int regnum)
>         {
>           if (regnum == i || regnum == -1)
>             {
> -             target_read_memory (sp + ((i - SPARC_L0_REGNUM) * 8), buf, 8);
> +             if (target_read_memory (sp + ((i - SPARC_L0_REGNUM) * 8), buf,
> 8) == -1)
> +               error (_("failed to read target memory at %s"),
> +                      core_addr_to_string (sp + ((i - SPARC_L0_REGNUM) *
> 8)));
>  
>               /* Handle StackGhost.  */
>               if (i == SPARC_I7_REGNUM)

Oh, it's bad that the return value of target_read_memory is not checked.  When
target_read_memory fails, that means we extract random bytes from `buf`.

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (8 preceding siblings ...)
  2021-02-23 18:32 ` simark at simark dot ca
@ 2021-02-23 18:33 ` simark at simark dot ca
  2021-02-24  9:50 ` andrew.burgess at embecosm dot com
                   ` (29 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: simark at simark dot ca @ 2021-02-23 18:33 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #10 from Simon Marchi <simark at simark dot ca> ---
(In reply to Andrew Burgess from comment #8)
> I'm testing this possible patch:
> 
> diff --git a/gdb/sparc-tdep.c b/gdb/sparc-tdep.c
> index 4f9c679b55c..6f6157fc461 100644
> --- a/gdb/sparc-tdep.c
> +++ b/gdb/sparc-tdep.c
> @@ -1948,6 +1948,11 @@ sparc_supply_rwindow (struct regcache *regcache,
> CORE_ADDR sp, int regnum)
>    gdb_byte buf[8];
>    int i;
>  
> +  /* Ensure the correct inferior_ptid is in place before calling target
> +     methods.  */
> +  scoped_restore save_inferior_ptid = make_scoped_restore (&inferior_ptid);
> +  inferior_ptid = regcache->ptid ();
> +
>    if (sp & 1)
>      {
>        /* Registers are 64-bit.  */

It's curious, isn't inferior_ptid set earlier, when "backtrace_command_1" runs?

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (9 preceding siblings ...)
  2021-02-23 18:33 ` simark at simark dot ca
@ 2021-02-24  9:50 ` andrew.burgess at embecosm dot com
  2021-02-24 21:34 ` simark at simark dot ca
                   ` (28 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: andrew.burgess at embecosm dot com @ 2021-02-24  9:50 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #11 from Andrew Burgess <andrew.burgess at embecosm dot com> ---
The problem is that the registers that "go wrong" are part of frame #0, which
are fetched when GDB first stops.  As such they end up being fetched in a call
tree that originates from the ::wait, like this:

#0  sparc_supply_rwindow (regcache=0x10001187fa0, sp=8791798050576, regnum=-1)
at ../../src/gdb/sparc-tdep.c:1967
#1  0x000001000076171c in sparc64_supply_gregset (gregmap=0x10000be0b5c
<sparc64_linux_ptrace_gregmap>, 
    regcache=0x10001187fa0, regnum=-1, gregs=0x7feffffd260) at
../../src/gdb/sparc64-tdep.c:1974
#2  0x0000010000751094 in sparc_fetch_inferior_registers
(regcache=0x10001187fa0, regnum=80)
    at ../../src/gdb/sparc-nat.c:170
#3  0x00000100007593f8 in sparc64_linux_nat_target::fetch_registers (
    this=0x10000fa0c40 <the_sparc64_linux_nat_target>, regcache=0x10001187fa0,
regnum=80)
    at ../../src/gdb/sparc64-linux-nat.c:38
#4  0x0000010000813d30 in target_fetch_registers (regcache=0x10001187fa0,
regno=80) at ../../src/gdb/target.c:3281
#5  0x00000100006a8194 in regcache::raw_update (this=0x10001187fa0, regnum=80)
at ../../src/gdb/regcache.c:584
#6  0x00000100006a82cc in readable_regcache::raw_read (this=0x10001187fa0,
regnum=80, buf=0x7feffffd7f0 "")
    at ../../src/gdb/regcache.c:598
#7  0x00000100006a88f0 in readable_regcache::cooked_read (this=0x10001187fa0,
regnum=80, buf=0x7feffffd7f0 "")
    at ../../src/gdb/regcache.c:690
#8  0x00000100006b1dc4 in readable_regcache::cooked_read<unsigned long, void>
(this=0x10001187fa0, regnum=80, 
    val=0x7feffffd978) at ../../src/gdb/regcache.c:777
#9  0x00000100006a907c in regcache_cooked_read_unsigned
(regcache=0x10001187fa0, regnum=80, val=0x7feffffd978)
    at ../../src/gdb/regcache.c:791
#10 0x00000100006ab474 in regcache_read_pc (regcache=0x10001187fa0) at
../../src/gdb/regcache.c:1295
#11 0x0000010000507218 in save_stop_reason (lp=0x1000121f190) at
../../src/gdb/linux-nat.c:2612
#12 0x0000010000508ee0 in linux_nat_filter_event (lwpid=3400064, status=1407)
at ../../src/gdb/linux-nat.c:3049
#13 0x00000100005098ac in linux_nat_wait_1 (ptid=..., ourstatus=0x7feffffe920,
target_options=...)
    at ../../src/gdb/linux-nat.c:3194
#14 0x000001000050aae0 in linux_nat_target::wait (this=0x10000fa0c40
<the_sparc64_linux_nat_target>, ptid=..., 
    ourstatus=0x7feffffe920, target_options=...) at
../../src/gdb/linux-nat.c:3432
#15 0x00000100007f810c in target_wait (ptid=..., status=0x7feffffe920,
options=...) at ../../src/gdb/target.c:1994
#16 0x00000100004aba74 in do_target_wait_1 (inf=0x1000116b140, ptid=...,
status=0x7feffffe920, options=...)
    at ../../src/gdb/infrun.c:3464
#17 0x00000100004abcb0 in operator() (__closure=0x7feffffe6a8,
inf=0x1000116b140) at ../../src/gdb/infrun.c:3527
#18 0x00000100004ac0c4 in do_target_wait (wait_ptid=..., ecs=0x7feffffe8f8,
options=...)
    at ../../src/gdb/infrun.c:3540
#19 0x00000100004ad1bc in fetch_inferior_event () at
../../src/gdb/infrun.c:3880
#20 0x0000010000484e60 in inferior_event_handler (event_type=INF_REG_EVENT) at
../../src/gdb/inf-loop.c:42
#21 0x00000100004be90c in infrun_async_inferior_event_handler (data=0x0) at
../../src/gdb/infrun.c:9216
#22 0x000001000012e9bc in check_async_event_handlers () at
../../src/gdb/async-event.c:327
#23 0x0000010000ab3ed4 in gdb_do_one_event () at
../../src/gdbsupport/event-loop.cc:216
#24 0x0000010000541f78 in start_event_loop () at ../../src/gdb/main.c:348
#25 0x000001000054218c in captured_command_loop () at ../../src/gdb/main.c:408
#26 0x0000010000544794 in captured_main (data=0x7fefffff0a8) at
../../src/gdb/main.c:1242
#27 0x000001000054483c in gdb_main (args=0x7fefffff0a8) at
../../src/gdb/main.c:1257
#28 0x00000100000c1f14 in main (argc=4, argv=0x7fefffff468) at
../../src/gdb/gdb.c:32

When we go into the wait inferior_ptid is always set to null_ptid, which makes
sense, as we don't know which inferior will be giving us an event.  It appears
that everything called from the wait, once we do know which inferior has
stopped, still has inferior_ptid set to null_ptid.

Having thought about my fix a little more I do wonder if we should move the
setting of inferior_ptid further up the call stack.  Given that inferior_ptid
does need to be set when making target_* calls, I'm tempted to say we should
really set inferior_ptid possibly as early as the ::wait, once we have figured
out which inferior the event is for.

Have reviewed the test results, and it looks pretty good.  Failures on sparc64
dropped from 7k+ to ~1.5k.

One further note, placing the error where I did (after the target read) has an
unfortunate effect that it prevents the target from stopping, here's a broken
session:

 (gdb) b puts
 Breakpoint 1 at 0x108de4
 (gdb) r
 Starting program: /home/aburgess/project/binutils-gdb/test/gdb-test.static 
 failed to read target memory at 0x000007feffffeef0
 (gdb) bt
 Selected thread is running.
 (gdb) 

Obviously this isn't a problem once we fix the setting of inferior_ptid, but it
still feels kind of rubbish.  I think a much better solution is:

diff --git a/gdb/sparc-tdep.c b/gdb/sparc-tdep.c
index 4f9c679b55c..78f93b121c8 100644
--- a/gdb/sparc-tdep.c
+++ b/gdb/sparc-tdep.c
@@ -1957,7 +1962,14 @@ sparc_supply_rwindow (struct regcache *regcache,
CORE_ADDR sp, int regnum)
        {
          if (regnum == i || regnum == -1)
            {
-             target_read_memory (sp + ((i - SPARC_L0_REGNUM) * 8), buf, 8);
+             if (target_read_memory (sp + ((i - SPARC_L0_REGNUM) * 8), buf, 8)
== -1)
+               {
+                 warning (_("failed to read 8 bytes of target memory at %s for
register %s"),
+                          core_addr_to_string (sp + ((i - SPARC_L0_REGNUM) *
8)),
+                          gdbarch_register_name (gdbarch, i));
+                 regcache->raw_supply (i, nullptr);
+                 continue;
+               }

              /* Handle StackGhost.  */
              if (i == SPARC_I7_REGNUM)

Now the register are just marked as unavailable.

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (10 preceding siblings ...)
  2021-02-24  9:50 ` andrew.burgess at embecosm dot com
@ 2021-02-24 21:34 ` simark at simark dot ca
  2021-02-24 23:39 ` simark at simark dot ca
                   ` (27 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: simark at simark dot ca @ 2021-02-24 21:34 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #12 from Simon Marchi <simark at simark dot ca> ---
Ah ok I see, indeed at the start of ::wait inferior_ptid isn't set.

> Having thought about my fix a little more I do wonder if we should move the
> setting of inferior_ptid further up the call stack.  Given that
> inferior_ptid does need to be set when making target_* calls, I'm tempted to
> say we should really set inferior_ptid possibly as early as the ::wait, once
> we have figured out which inferior the event is for.

I'd prefer for us to move in the opposite direction, making target methods less
and less dependent on inferior_ptid.  Ultimately, we would like (I think) that
no target methods rely on the value of inferior_ptid on entry, instead passing
the ptid (or inferior pointer or thread_info pointer) by parameter.  I think
it's impossible to do all that work in one shot, so the alternative is to
convert methods incrementally.  But so far it's not clear which methods need to
be called with inferior_ptid set correctly and which methods don't, what is the
contract between a target method and its callers.  In my mind, fetch_registers
didn't need inferior_ptid to be set, but you just found out that it's not true,
because one implementation calls target_read_memory, and that one is dependent
on inferior_ptid.

To make forward progress towards the goal of relying less on inferior_ptid, I
suggest that we keep the assumption that calling the fetch_registers method
doesn't need inferior_ptid to be set.  If a particular implementation needs to
call some other functions which are inferior_ptid-sensitive, then it would be
responsible for temporarily switching the global context to the correct thread.
 As time passes and we make more and more functions independent of
inferior_ptid, we can move this global thread-switching to narrower and
narrower scopes, until they disappear completely.

On problem I see is that it's difficult to know which method/function depends
on the global thread / inferior_ptid.  IWBN to have a way to mark (with a
comment or attribute) functions and methods to say that they do.  When calling
a marked function from an unmarked function, you know you need to switch the
global thread for the duration of the scope.

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (11 preceding siblings ...)
  2021-02-24 21:34 ` simark at simark dot ca
@ 2021-02-24 23:39 ` simark at simark dot ca
  2021-03-04  0:49 ` simark at simark dot ca
                   ` (26 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: simark at simark dot ca @ 2021-02-24 23:39 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #13 from Simon Marchi <simark at simark dot ca> ---
Created attachment 13261
  --> https://sourceware.org/bugzilla/attachment.cgi?id=13261&action=edit
Proposed patch (Simon)

Here's what I have to propose based on my previous comment.  This is the
narrowest scope where I managed to put the switch_to_thread that didn't require
a massive refactor.  I think that can be removed once the memory
reading/writing code (well, everything that uses xfer_partial) doesn't rely on
the global context.  Regarding this, I'd like to get back to this patch
eventually:

https://sourceware.org/pipermail/gdb-patches/2020-August/171215.html

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (12 preceding siblings ...)
  2021-02-24 23:39 ` simark at simark dot ca
@ 2021-03-04  0:49 ` simark at simark dot ca
  2021-03-04 12:27 ` koachan+sourceware at protonmail dot com
                   ` (25 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: simark at simark dot ca @ 2021-03-04  0:49 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #14 from Simon Marchi <simark at simark dot ca> ---
Patch posted here, feedback is welcome!

https://sourceware.org/pipermail/gdb-patches/2021-March/176752.html

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (13 preceding siblings ...)
  2021-03-04  0:49 ` simark at simark dot ca
@ 2021-03-04 12:27 ` koachan+sourceware at protonmail dot com
  2021-03-04 16:07 ` cvs-commit at gcc dot gnu.org
                   ` (24 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: koachan+sourceware at protonmail dot com @ 2021-03-04 12:27 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #15 from Koakuma <koachan+sourceware at protonmail dot com> ---
(In reply to Simon Marchi from comment #14)
> Patch posted here, feedback is welcome!
> 
> https://sourceware.org/pipermail/gdb-patches/2021-March/176752.html

Thanks for the patch, it seems to work okay here, at least:

(gdb) break puts
Breakpoint 1 at 0x108114: file ioputs.c, line 33.
(gdb) continue
Continuing.

Breakpoint 1, _IO_puts (str=0x16c498 "Hello world!\n") at ioputs.c:33
33      {
(gdb) backtrace
#0  _IO_puts (str=0x16c498 "Hello world!\n") at ioputs.c:33
#1  0x0000000000100930 in hello () at gdb-test.c:4
#2  0x0000000000100948 in main () at gdb-test.c:8

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (14 preceding siblings ...)
  2021-03-04 12:27 ` koachan+sourceware at protonmail dot com
@ 2021-03-04 16:07 ` cvs-commit at gcc dot gnu.org
  2021-03-04 17:08 ` cvs-commit at gcc dot gnu.org
                   ` (23 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2021-03-04 16:07 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #16 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Simon Marchi <simark@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d1e93af64a6b74921cca9bca8a7043855f9da10d

commit d1e93af64a6b74921cca9bca8a7043855f9da10d
Author: Simon Marchi <simon.marchi@polymtl.ca>
Date:   Thu Mar 4 10:57:03 2021 -0500

    gdb: set current thread in sparc_{fetch,collect}_inferior_registers (PR
gdb/27147)

    PR 27147 shows that on sparc64, GDB is unable to properly unwind:

    Expected result (from GDB 9.2):

        #0  0x0000000000108de4 in puts ()
        #1  0x0000000000100950 in hello () at gdb-test.c:4
        #2  0x0000000000100968 in main () at gdb-test.c:8

    Actual result (from GDB latest git):

        #0  0x0000000000108de4 in puts ()
        #1  0x0000000000100950 in hello () at gdb-test.c:4
        Backtrace stopped: previous frame inner to this frame (corrupt stack?)

    The first failing commit is 5b6d1e4fa4fc ("Multi-target support").  The
cause
    of the change in behavior is due to (thanks for Andrew Burgess for finding
    this):

     - inferior_ptid is no longer set on entry of target_ops::wait, whereas
       it was set to something valid previously
     - deep down in linux_nat_target::wait (see stack trace below), we fetch
       the registers of the event thread
     - on sparc64, fetching registers involves reading memory (in
       sparc_supply_rwindow, see stack trace below)
     - reading memory (target_ops::xfer_partial) relies on inferior_ptid
       being set to the thread from which we want to read memory

    This is where things go wrong:

        #0  linux_nat_target::xfer_partial (this=0x10000fa2c40
<the_sparc64_linux_nat_target>, object=TARGET_OBJECT_MEMORY, annex=0x0,
readbuf=0x7feffe3b000 "", writebuf=0x0, offset=8791798050744, len=8,
xfered_len=0x7feffe3ae88) at /home/simark/src/binutils-gdb/gdb/linux-nat.c:3697
        #1  0x00000100007f5b10 in raw_memory_xfer_partial (ops=0x10000fa2c40
<the_sparc64_linux_nat_target>, readbuf=0x7feffe3b000 "", writebuf=0x0,
memaddr=8791798050744, len=8, xfered_len=0x7feffe3ae88) at
/home/simark/src/binutils-gdb/gdb/target.c:912
        #2  0x00000100007f60e8 in memory_xfer_partial_1 (ops=0x10000fa2c40
<the_sparc64_linux_nat_target>, object=TARGET_OBJECT_MEMORY,
readbuf=0x7feffe3b000 "", writebuf=0x0, memaddr=8791798050744, len=8,
xfered_len=0x7feffe3ae88) at /home/simark/src/binutils-gdb/gdb/target.c:1043
        #3  0x00000100007f61b4 in memory_xfer_partial (ops=0x10000fa2c40
<the_sparc64_linux_nat_target>, object=TARGET_OBJECT_MEMORY,
readbuf=0x7feffe3b000 "", writebuf=0x0, memaddr=8791798050744, len=8,
xfered_len=0x7feffe3ae88) at /home/simark/src/binutils-gdb/gdb/target.c:1072
        #4  0x00000100007f6538 in target_xfer_partial (ops=0x10000fa2c40
<the_sparc64_linux_nat_target>, object=TARGET_OBJECT_MEMORY, annex=0x0,
readbuf=0x7feffe3b000 "", writebuf=0x0, offset=8791798050744, len=8,
xfered_len=0x7feffe3ae88) at /home/simark/src/binutils-gdb/gdb/target.c:1129
        #5  0x00000100007f7094 in target_read_partial (ops=0x10000fa2c40
<the_sparc64_linux_nat_target>, object=TARGET_OBJECT_MEMORY, annex=0x0,
buf=0x7feffe3b000 "", offset=8791798050744, len=8, xfered_len=0x7feffe3ae88) at
/home/simark/src/binutils-gdb/gdb/target.c:1375
        #6  0x00000100007f721c in target_read (ops=0x10000fa2c40
<the_sparc64_linux_nat_target>, object=TARGET_OBJECT_MEMORY, annex=0x0,
buf=0x7feffe3b000 "", offset=8791798050744, len=8) at
/home/simark/src/binutils-gdb/gdb/target.c:1415
        #7  0x00000100007f69d4 in target_read_memory (memaddr=8791798050744,
myaddr=0x7feffe3b000 "", len=8) at
/home/simark/src/binutils-gdb/gdb/target.c:1218
        #8  0x0000010000758520 in sparc_supply_rwindow (regcache=0x10000fea4f0,
sp=8791798050736, regnum=-1) at
/home/simark/src/binutils-gdb/gdb/sparc-tdep.c:1960
        #9  0x000001000076208c in sparc64_supply_gregset (gregmap=0x10000be3190
<sparc64_linux_ptrace_gregmap>, regcache=0x10000fea4f0, regnum=-1,
gregs=0x7feffe3b230) at /home/simark/src/binutils-gdb/gdb/sparc64-tdep.c:1974
        #10 0x0000010000751b64 in sparc_fetch_inferior_registers
(regcache=0x10000fea4f0, regnum=80) at
/home/simark/src/binutils-gdb/gdb/sparc-nat.c:170
        #11 0x0000010000759d68 in sparc64_linux_nat_target::fetch_registers
(this=0x10000fa2c40 <the_sparc64_linux_nat_target>, regcache=0x10000fea4f0,
regnum=80) at /home/simark/src/binutils-gdb/gdb/sparc64-linux-nat.c:38
        #12 0x00000100008146ec in target_fetch_registers
(regcache=0x10000fea4f0, regno=80) at
/home/simark/src/binutils-gdb/gdb/target.c:3287
        #13 0x00000100006a8c5c in regcache::raw_update (this=0x10000fea4f0,
regnum=80) at /home/simark/src/binutils-gdb/gdb/regcache.c:584
        #14 0x00000100006a8d94 in readable_regcache::raw_read
(this=0x10000fea4f0, regnum=80, buf=0x7feffe3b7c0 "") at
/home/simark/src/binutils-gdb/gdb/regcache.c:598
        #15 0x00000100006a93b8 in readable_regcache::cooked_read
(this=0x10000fea4f0, regnum=80, buf=0x7feffe3b7c0 "") at
/home/simark/src/binutils-gdb/gdb/regcache.c:690
        #16 0x00000100006b288c in readable_regcache::cooked_read<unsigned long,
void> (this=0x10000fea4f0, regnum=80, val=0x7feffe3b948) at
/home/simark/src/binutils-gdb/gdb/regcache.c:777
        #17 0x00000100006a9b44 in regcache_cooked_read_unsigned
(regcache=0x10000fea4f0, regnum=80, val=0x7feffe3b948) at
/home/simark/src/binutils-gdb/gdb/regcache.c:791
        #18 0x00000100006abf3c in regcache_read_pc (regcache=0x10000fea4f0) at
/home/simark/src/binutils-gdb/gdb/regcache.c:1295
        #19 0x0000010000507920 in save_stop_reason (lp=0x10000fc5b10) at
/home/simark/src/binutils-gdb/gdb/linux-nat.c:2612
        #20 0x00000100005095a4 in linux_nat_filter_event (lwpid=520983,
status=1407) at /home/simark/src/binutils-gdb/gdb/linux-nat.c:3050
        #21 0x0000010000509f9c in linux_nat_wait_1 (ptid=...,
ourstatus=0x7feffe3c8f0, target_options=...) at
/home/simark/src/binutils-gdb/gdb/linux-nat.c:3194
        #22 0x000001000050b1d0 in linux_nat_target::wait (this=0x10000fa2c40
<the_sparc64_linux_nat_target>, ptid=..., ourstatus=0x7feffe3c8f0,
target_options=...) at /home/simark/src/binutils-gdb/gdb/linux-nat.c:3432
        #23 0x00000100007f8ac0 in target_wait (ptid=..., status=0x7feffe3c8f0,
options=...) at /home/simark/src/binutils-gdb/gdb/target.c:2000
        #24 0x00000100004ac17c in do_target_wait_1 (inf=0x1000116d280,
ptid=..., status=0x7feffe3c8f0, options=...) at
/home/simark/src/binutils-gdb/gdb/infrun.c:3464
        #25 0x00000100004ac3b8 in operator() (__closure=0x7feffe3c678,
inf=0x1000116d280) at /home/simark/src/binutils-gdb/gdb/infrun.c:3527
        #26 0x00000100004ac7cc in do_target_wait (wait_ptid=...,
ecs=0x7feffe3c8c8, options=...) at
/home/simark/src/binutils-gdb/gdb/infrun.c:3540
        #27 0x00000100004ad8c4 in fetch_inferior_event () at
/home/simark/src/binutils-gdb/gdb/infrun.c:3880
        #28 0x0000010000485568 in inferior_event_handler
(event_type=INF_REG_EVENT) at /home/simark/src/binutils-gdb/gdb/inf-loop.c:42
        #29 0x000001000050d394 in handle_target_event (error=0,
client_data=0x0) at /home/simark/src/binutils-gdb/gdb/linux-nat.c:4060
        #30 0x0000010000ab5c8c in handle_file_event (file_ptr=0x10001207270,
ready_mask=1) at /home/simark/src/binutils-gdb/gdbsupport/event-loop.cc:575
        #31 0x0000010000ab6334 in gdb_wait_for_event (block=0) at
/home/simark/src/binutils-gdb/gdbsupport/event-loop.cc:701
        #32 0x0000010000ab487c in gdb_do_one_event () at
/home/simark/src/binutils-gdb/gdbsupport/event-loop.cc:212
        #33 0x0000010000542668 in start_event_loop () at
/home/simark/src/binutils-gdb/gdb/main.c:348
        #34 0x000001000054287c in captured_command_loop () at
/home/simark/src/binutils-gdb/gdb/main.c:408
        #35 0x0000010000544e84 in captured_main (data=0x7feffe3d188) at
/home/simark/src/binutils-gdb/gdb/main.c:1242
        #36 0x0000010000544f2c in gdb_main (args=0x7feffe3d188) at
/home/simark/src/binutils-gdb/gdb/main.c:1257
        #37 0x00000100000c1f14 in main (argc=4, argv=0x7feffe3d548) at
/home/simark/src/binutils-gdb/gdb/gdb.c:32

    There is a target_read_memory call in sparc_supply_rwindow, whose return
    value is not checked.  That call fails, because inferior_ptid does not
    contain a valid ptid, and uninitialized buffer contents is used.
    Ultimately it results in a corrupt stop_pc.

    target_ops::fetch_registers can be (and should remain, in my opinion)
    independent of inferior_ptid, because the ptid of the thread from which
    to fetch registers can be obtained from the regcache.  In other words,
    implementations of target_ops::fetch_registers should not rely on
    inferior_ptid having a sensible value on entry.

    The sparc64_linux_nat_target::fetch_registers case is special, because it
calls
    a target method that is dependent on the inferior_ptid value
    (target_read_inferior, and ultimately target_ops::xfer_partial).  So I
would
    say it's the responsibility of sparc64_linux_nat_target::fetch_registers to
set
    up inferior_ptid correctly prior to calling target_read_inferior.

    This patch makes sparc64_linux_nat_target::fetch_registers (and
    store_registers, since it works the same) temporarily set inferior_ptid. 
If we
    ever make target_ops::xfer_partial independent of inferior_ptid, setting
    inferior_ptid won't be necessary, we'll simply pass down the ptid as a
    parameter in some way.

    I chose to set/restore inferior_ptid in sparc_fetch_inferior_registers,
because
    I am not convinced that doing so in an inner location (in
sparc_supply_rwindow
    for instance) would always be correct.  We have access to the ptid in
    sparc_supply_rwindow (from the regcache), so we _could_ set inferior_ptid
    there.  However, I don't want to just set inferior_ptid, as that would make
it
    not desync'ed with `current_thread ()` and `current_inferior ()`.  It's
    preferable to use switch_to_thread instead, as that switches all the global
    "current" stuff in a coherent way.  But doing so requires a `thread_info
*`,
    and getting a `thread_info *` from a ptid requires a
`process_stratum_target
    *`.  We could use `current_inferior()->process_target()` in
    sparc_supply_rwindow for this (using target_read_memory uses the current
    inferior's target stack anyway).  However, sparc_supply_rwindow is also
used in
    the context of BSD uthreads, where a thread stratum target defines threads.
 I
    presume the ptid in the regcache would be the ptid of the uthread, defined
by
    the thread stratum target (bsd_uthread_target).  Using
    `current_inferior()->process_target()` would look up a ptid defined by the
    thread stratum target using the process stratum target.  I don't think it
would
    give good results.  So I prefer playing it safe and looking up the thread
    earlier, in sparc_fetch_inferior_registers.

    I added some assertions (in sparc_supply_rwindow and others) to verify
    that the regcache's ptid matches inferior_ptid.  That verifies that the
    caller has properly set the correct global context.  This would have
    caught (though a failed assertion) the current problem.

    gdb/ChangeLog:

            PR gdb/27147
            * sparc-nat.h (sparc_fetch_inferior_registers): Add
            process_stratum_target parameter,
            sparc_store_inferior_registers): update callers.
            * sparc-nat.c (sparc_fetch_inferior_registers,
            sparc_store_inferior_registers): Add process_stratum_target
            parameter.  Switch current thread before calling
            sparc_supply_gregset / sparc_collect_rwindow.
            (sparc_store_inferior_registers): Likewise.
            * sparc-obsd-tdep.c (sparc32obsd_supply_uthread): Add assertion.
            (sparc32obsd_collect_uthread): Likewise.
            * sparc-tdep.c (sparc_supply_rwindow, sparc_collect_rwindow):
            Add assertion.
            * sparc64-obsd-tdep.c (sparc64obsd_collect_uthread,
            sparc64obsd_supply_uthread): Add assertion.

    Change-Id: I16c658cd70896cea604516714f7e2428fbaf4301

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (15 preceding siblings ...)
  2021-03-04 16:07 ` cvs-commit at gcc dot gnu.org
@ 2021-03-04 17:08 ` cvs-commit at gcc dot gnu.org
  2021-03-04 17:09 ` simark at simark dot ca
                   ` (22 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2021-03-04 17:08 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #17 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The gdb-10-branch branch has been updated by Simon Marchi
<simark@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ffc17e2c029aea90166d16f5d49503c2c2e20982

commit ffc17e2c029aea90166d16f5d49503c2c2e20982
Author: Simon Marchi <simon.marchi@polymtl.ca>
Date:   Thu Mar 4 10:57:03 2021 -0500

    gdb: set current thread in sparc_{fetch,collect}_inferior_registers (PR
gdb/27147)

    PR 27147 shows that on sparc64, GDB is unable to properly unwind:

    Expected result (from GDB 9.2):

        #0  0x0000000000108de4 in puts ()
        #1  0x0000000000100950 in hello () at gdb-test.c:4
        #2  0x0000000000100968 in main () at gdb-test.c:8

    Actual result (from GDB latest git):

        #0  0x0000000000108de4 in puts ()
        #1  0x0000000000100950 in hello () at gdb-test.c:4
        Backtrace stopped: previous frame inner to this frame (corrupt stack?)

    The first failing commit is 5b6d1e4fa4fc ("Multi-target support").  The
cause
    of the change in behavior is due to (thanks for Andrew Burgess for finding
    this):

     - inferior_ptid is no longer set on entry of target_ops::wait, whereas
       it was set to something valid previously
     - deep down in linux_nat_target::wait (see stack trace below), we fetch
       the registers of the event thread
     - on sparc64, fetching registers involves reading memory (in
       sparc_supply_rwindow, see stack trace below)
     - reading memory (target_ops::xfer_partial) relies on inferior_ptid
       being set to the thread from which we want to read memory

    This is where things go wrong:

        #0  linux_nat_target::xfer_partial (this=0x10000fa2c40
<the_sparc64_linux_nat_target>, object=TARGET_OBJECT_MEMORY, annex=0x0,
readbuf=0x7feffe3b000 "", writebuf=0x0, offset=8791798050744, len=8,
xfered_len=0x7feffe3ae88) at /home/simark/src/binutils-gdb/gdb/linux-nat.c:3697
        #1  0x00000100007f5b10 in raw_memory_xfer_partial (ops=0x10000fa2c40
<the_sparc64_linux_nat_target>, readbuf=0x7feffe3b000 "", writebuf=0x0,
memaddr=8791798050744, len=8, xfered_len=0x7feffe3ae88) at
/home/simark/src/binutils-gdb/gdb/target.c:912
        #2  0x00000100007f60e8 in memory_xfer_partial_1 (ops=0x10000fa2c40
<the_sparc64_linux_nat_target>, object=TARGET_OBJECT_MEMORY,
readbuf=0x7feffe3b000 "", writebuf=0x0, memaddr=8791798050744, len=8,
xfered_len=0x7feffe3ae88) at /home/simark/src/binutils-gdb/gdb/target.c:1043
        #3  0x00000100007f61b4 in memory_xfer_partial (ops=0x10000fa2c40
<the_sparc64_linux_nat_target>, object=TARGET_OBJECT_MEMORY,
readbuf=0x7feffe3b000 "", writebuf=0x0, memaddr=8791798050744, len=8,
xfered_len=0x7feffe3ae88) at /home/simark/src/binutils-gdb/gdb/target.c:1072
        #4  0x00000100007f6538 in target_xfer_partial (ops=0x10000fa2c40
<the_sparc64_linux_nat_target>, object=TARGET_OBJECT_MEMORY, annex=0x0,
readbuf=0x7feffe3b000 "", writebuf=0x0, offset=8791798050744, len=8,
xfered_len=0x7feffe3ae88) at /home/simark/src/binutils-gdb/gdb/target.c:1129
        #5  0x00000100007f7094 in target_read_partial (ops=0x10000fa2c40
<the_sparc64_linux_nat_target>, object=TARGET_OBJECT_MEMORY, annex=0x0,
buf=0x7feffe3b000 "", offset=8791798050744, len=8, xfered_len=0x7feffe3ae88) at
/home/simark/src/binutils-gdb/gdb/target.c:1375
        #6  0x00000100007f721c in target_read (ops=0x10000fa2c40
<the_sparc64_linux_nat_target>, object=TARGET_OBJECT_MEMORY, annex=0x0,
buf=0x7feffe3b000 "", offset=8791798050744, len=8) at
/home/simark/src/binutils-gdb/gdb/target.c:1415
        #7  0x00000100007f69d4 in target_read_memory (memaddr=8791798050744,
myaddr=0x7feffe3b000 "", len=8) at
/home/simark/src/binutils-gdb/gdb/target.c:1218
        #8  0x0000010000758520 in sparc_supply_rwindow (regcache=0x10000fea4f0,
sp=8791798050736, regnum=-1) at
/home/simark/src/binutils-gdb/gdb/sparc-tdep.c:1960
        #9  0x000001000076208c in sparc64_supply_gregset (gregmap=0x10000be3190
<sparc64_linux_ptrace_gregmap>, regcache=0x10000fea4f0, regnum=-1,
gregs=0x7feffe3b230) at /home/simark/src/binutils-gdb/gdb/sparc64-tdep.c:1974
        #10 0x0000010000751b64 in sparc_fetch_inferior_registers
(regcache=0x10000fea4f0, regnum=80) at
/home/simark/src/binutils-gdb/gdb/sparc-nat.c:170
        #11 0x0000010000759d68 in sparc64_linux_nat_target::fetch_registers
(this=0x10000fa2c40 <the_sparc64_linux_nat_target>, regcache=0x10000fea4f0,
regnum=80) at /home/simark/src/binutils-gdb/gdb/sparc64-linux-nat.c:38
        #12 0x00000100008146ec in target_fetch_registers
(regcache=0x10000fea4f0, regno=80) at
/home/simark/src/binutils-gdb/gdb/target.c:3287
        #13 0x00000100006a8c5c in regcache::raw_update (this=0x10000fea4f0,
regnum=80) at /home/simark/src/binutils-gdb/gdb/regcache.c:584
        #14 0x00000100006a8d94 in readable_regcache::raw_read
(this=0x10000fea4f0, regnum=80, buf=0x7feffe3b7c0 "") at
/home/simark/src/binutils-gdb/gdb/regcache.c:598
        #15 0x00000100006a93b8 in readable_regcache::cooked_read
(this=0x10000fea4f0, regnum=80, buf=0x7feffe3b7c0 "") at
/home/simark/src/binutils-gdb/gdb/regcache.c:690
        #16 0x00000100006b288c in readable_regcache::cooked_read<unsigned long,
void> (this=0x10000fea4f0, regnum=80, val=0x7feffe3b948) at
/home/simark/src/binutils-gdb/gdb/regcache.c:777
        #17 0x00000100006a9b44 in regcache_cooked_read_unsigned
(regcache=0x10000fea4f0, regnum=80, val=0x7feffe3b948) at
/home/simark/src/binutils-gdb/gdb/regcache.c:791
        #18 0x00000100006abf3c in regcache_read_pc (regcache=0x10000fea4f0) at
/home/simark/src/binutils-gdb/gdb/regcache.c:1295
        #19 0x0000010000507920 in save_stop_reason (lp=0x10000fc5b10) at
/home/simark/src/binutils-gdb/gdb/linux-nat.c:2612
        #20 0x00000100005095a4 in linux_nat_filter_event (lwpid=520983,
status=1407) at /home/simark/src/binutils-gdb/gdb/linux-nat.c:3050
        #21 0x0000010000509f9c in linux_nat_wait_1 (ptid=...,
ourstatus=0x7feffe3c8f0, target_options=...) at
/home/simark/src/binutils-gdb/gdb/linux-nat.c:3194
        #22 0x000001000050b1d0 in linux_nat_target::wait (this=0x10000fa2c40
<the_sparc64_linux_nat_target>, ptid=..., ourstatus=0x7feffe3c8f0,
target_options=...) at /home/simark/src/binutils-gdb/gdb/linux-nat.c:3432
        #23 0x00000100007f8ac0 in target_wait (ptid=..., status=0x7feffe3c8f0,
options=...) at /home/simark/src/binutils-gdb/gdb/target.c:2000
        #24 0x00000100004ac17c in do_target_wait_1 (inf=0x1000116d280,
ptid=..., status=0x7feffe3c8f0, options=...) at
/home/simark/src/binutils-gdb/gdb/infrun.c:3464
        #25 0x00000100004ac3b8 in operator() (__closure=0x7feffe3c678,
inf=0x1000116d280) at /home/simark/src/binutils-gdb/gdb/infrun.c:3527
        #26 0x00000100004ac7cc in do_target_wait (wait_ptid=...,
ecs=0x7feffe3c8c8, options=...) at
/home/simark/src/binutils-gdb/gdb/infrun.c:3540
        #27 0x00000100004ad8c4 in fetch_inferior_event () at
/home/simark/src/binutils-gdb/gdb/infrun.c:3880
        #28 0x0000010000485568 in inferior_event_handler
(event_type=INF_REG_EVENT) at /home/simark/src/binutils-gdb/gdb/inf-loop.c:42
        #29 0x000001000050d394 in handle_target_event (error=0,
client_data=0x0) at /home/simark/src/binutils-gdb/gdb/linux-nat.c:4060
        #30 0x0000010000ab5c8c in handle_file_event (file_ptr=0x10001207270,
ready_mask=1) at /home/simark/src/binutils-gdb/gdbsupport/event-loop.cc:575
        #31 0x0000010000ab6334 in gdb_wait_for_event (block=0) at
/home/simark/src/binutils-gdb/gdbsupport/event-loop.cc:701
        #32 0x0000010000ab487c in gdb_do_one_event () at
/home/simark/src/binutils-gdb/gdbsupport/event-loop.cc:212
        #33 0x0000010000542668 in start_event_loop () at
/home/simark/src/binutils-gdb/gdb/main.c:348
        #34 0x000001000054287c in captured_command_loop () at
/home/simark/src/binutils-gdb/gdb/main.c:408
        #35 0x0000010000544e84 in captured_main (data=0x7feffe3d188) at
/home/simark/src/binutils-gdb/gdb/main.c:1242
        #36 0x0000010000544f2c in gdb_main (args=0x7feffe3d188) at
/home/simark/src/binutils-gdb/gdb/main.c:1257
        #37 0x00000100000c1f14 in main (argc=4, argv=0x7feffe3d548) at
/home/simark/src/binutils-gdb/gdb/gdb.c:32

    There is a target_read_memory call in sparc_supply_rwindow, whose return
    value is not checked.  That call fails, because inferior_ptid does not
    contain a valid ptid, and uninitialized buffer contents is used.
    Ultimately it results in a corrupt stop_pc.

    target_ops::fetch_registers can be (and should remain, in my opinion)
    independent of inferior_ptid, because the ptid of the thread from which
    to fetch registers can be obtained from the regcache.  In other words,
    implementations of target_ops::fetch_registers should not rely on
    inferior_ptid having a sensible value on entry.

    The sparc64_linux_nat_target::fetch_registers case is special, because it
calls
    a target method that is dependent on the inferior_ptid value
    (target_read_inferior, and ultimately target_ops::xfer_partial).  So I
would
    say it's the responsibility of sparc64_linux_nat_target::fetch_registers to
set
    up inferior_ptid correctly prior to calling target_read_inferior.

    This patch makes sparc64_linux_nat_target::fetch_registers (and
    store_registers, since it works the same) temporarily set inferior_ptid. 
If we
    ever make target_ops::xfer_partial independent of inferior_ptid, setting
    inferior_ptid won't be necessary, we'll simply pass down the ptid as a
    parameter in some way.

    I chose to set/restore inferior_ptid in sparc_fetch_inferior_registers,
because
    I am not convinced that doing so in an inner location (in
sparc_supply_rwindow
    for instance) would always be correct.  We have access to the ptid in
    sparc_supply_rwindow (from the regcache), so we _could_ set inferior_ptid
    there.  However, I don't want to just set inferior_ptid, as that would make
it
    not desync'ed with `current_thread ()` and `current_inferior ()`.  It's
    preferable to use switch_to_thread instead, as that switches all the global
    "current" stuff in a coherent way.  But doing so requires a `thread_info
*`,
    and getting a `thread_info *` from a ptid requires a
`process_stratum_target
    *`.  We could use `current_inferior()->process_target()` in
    sparc_supply_rwindow for this (using target_read_memory uses the current
    inferior's target stack anyway).  However, sparc_supply_rwindow is also
used in
    the context of BSD uthreads, where a thread stratum target defines threads.
 I
    presume the ptid in the regcache would be the ptid of the uthread, defined
by
    the thread stratum target (bsd_uthread_target).  Using
    `current_inferior()->process_target()` would look up a ptid defined by the
    thread stratum target using the process stratum target.  I don't think it
would
    give good results.  So I prefer playing it safe and looking up the thread
    earlier, in sparc_fetch_inferior_registers.

    I added some assertions (in sparc_supply_rwindow and others) to verify
    that the regcache's ptid matches inferior_ptid.  That verifies that the
    caller has properly set the correct global context.  This would have
    caught (though a failed assertion) the current problem.

    gdb/ChangeLog:

            PR gdb/27147
            * sparc-nat.h (sparc_fetch_inferior_registers): Add
            process_stratum_target parameter,
            sparc_store_inferior_registers): update callers.
            * sparc-nat.c (sparc_fetch_inferior_registers,
            sparc_store_inferior_registers): Add process_stratum_target
            parameter.  Switch current thread before calling
            sparc_supply_gregset / sparc_collect_rwindow.
            (sparc_store_inferior_registers): Likewise.
            * sparc-obsd-tdep.c (sparc32obsd_supply_uthread): Add assertion.
            (sparc32obsd_collect_uthread): Likewise.
            * sparc-tdep.c (sparc_supply_rwindow, sparc_collect_rwindow):
            Add assertion.
            * sparc64-obsd-tdep.c (sparc64obsd_collect_uthread,
            sparc64obsd_supply_uthread): Add assertion.

    Change-Id: I16c658cd70896cea604516714f7e2428fbaf4301

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (16 preceding siblings ...)
  2021-03-04 17:08 ` cvs-commit at gcc dot gnu.org
@ 2021-03-04 17:09 ` simark at simark dot ca
  2021-03-04 17:09 ` simark at simark dot ca
                   ` (21 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: simark at simark dot ca @ 2021-03-04 17:09 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #18 from Simon Marchi <simark at simark dot ca> ---
Fixed.

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (17 preceding siblings ...)
  2021-03-04 17:09 ` simark at simark dot ca
@ 2021-03-04 17:09 ` simark at simark dot ca
  2021-06-27 17:46 ` ahmedsayeed1982 at yahoo dot com
                   ` (20 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: simark at simark dot ca @ 2021-03-04 17:09 UTC (permalink / raw)
  To: gdb-prs

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

Simon Marchi <simark at simark dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #19 from Simon Marchi <simark at simark dot ca> ---
Woops, fixed.

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (18 preceding siblings ...)
  2021-03-04 17:09 ` simark at simark dot ca
@ 2021-06-27 17:46 ` ahmedsayeed1982 at yahoo dot com
  2021-08-10 11:45 ` ucelsanicin at yahoo dot com
                   ` (19 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: ahmedsayeed1982 at yahoo dot com @ 2021-06-27 17:46 UTC (permalink / raw)
  To: gdb-prs

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

Ahmed Sayeed <ahmedsayeed1982 at yahoo dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ahmedsayeed1982 at yahoo dot com

--- Comment #20 from Ahmed Sayeed <ahmedsayeed1982 at yahoo dot com> ---
Expected result (from GDB 9.2):
#0  0x0000000000108de4 in puts ()
#1  0x0000000000100950 in hello () at gdb-test.c:4
#2  0x0000000000100968 in main () at gdb-test.c:8

Actual result (from GDB latest git):
#0  0x0000000000108de4 in puts ()
#1  0x0000000000100950 in hello () at gdb-test.c:4
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Worked fine on 9.2, started experiencing problem in 10.1, and it seems that
latest git version (11.0.50.20210104-git, commit
e9cf3691bfa140469d52815a2307b00eecf7917c)
is still problematic.

http://betwsycoednet.online

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (19 preceding siblings ...)
  2021-06-27 17:46 ` ahmedsayeed1982 at yahoo dot com
@ 2021-08-10 11:45 ` ucelsanicin at yahoo dot com
  2021-08-27 17:52 ` ribevi6798 at enamelme dot com
                   ` (18 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: ucelsanicin at yahoo dot com @ 2021-08-10 11:45 UTC (permalink / raw)
  To: gdb-prs

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

Ucel Sani <ucelsanicin at yahoo dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ucelsanicin at yahoo dot com

--- Comment #21 from Ucel Sani <ucelsanicin at yahoo dot com> ---
https://komiya-dental.com/
http://steemfilter.space/
http://michielleunens.tech/
http://sleepypoetstuff.website/
http://biciclubvalencia.website/
http://reputation-management.site/
http://pitesti.online/
http://tobuweb.space/
http://ancientmariners.online/
http://kuzin.website
http://kundaliniyoga.tech
http://localpay.tech
http://my-iframe.online
http://getimov.xyz/
http://ooviv.xyz/
http://mirei.xyz
http://toblek.xyz/
http://sevenwonders.store
http://peralga.xyz/
https://texastourgear.live
http://freixenet.site/influencerprogramme/
http://timvanorden.store/
http://rhee.tech/
http://f3group.online/
https://www.hlungomare.store/
https://www.lungomarebikehotel.store
http://www.lvmaimai.xyz/
https://sozdanie.site/
http://agens128.site/
http://troubadourtunes.online/
http://ruirui.store/
http://www.foamhands.store/
http://www.i-obchody.info/
http://naughtyrobot.digital/
https://www.webb-dev.co.uk/
https://waytowhatsnext.com/
https://www.bilanmagazine.com/
https://www.web-mediaplacing.com/
https://fitnessblog.fr/
https://cbd-huile-blog.fr/
https://www.laptopkerja.com/
https://www.espresso-international.eu/
https://www.espresso-international.be
https://www.espresso-international.gr
https://besthotels.wiki
https://www.cherada.net/opus/verified-gmail-accounts
https://www.cherada.net/opus/10000-visitas-a-tu-video-en-youtube
https://www.cherada.net/opus/100-backlinks-en-comentarios-de-blog-a-la-medida
https://redwinecasino.com/
https://sharkcasinogames.com/
https://redbettips.com/
https://windows11iso.com/

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (20 preceding siblings ...)
  2021-08-10 11:45 ` ucelsanicin at yahoo dot com
@ 2021-08-27 17:52 ` ribevi6798 at enamelme dot com
  2021-08-28 18:31 ` buranlevent at yahoo dot com
                   ` (17 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: ribevi6798 at enamelme dot com @ 2021-08-27 17:52 UTC (permalink / raw)
  To: gdb-prs

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

ribevi <ribevi6798 at enamelme dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ribevi6798 at enamelme dot com

--- Comment #22 from ribevi <ribevi6798 at enamelme dot com> ---
Positive site, where did u come up with the information on this posting?I have
read a few of the articles on your website now, and I really like your style.
Thanks a million and please keep up the effective work.
https://www.introverts.org
https://imedenver.com/
https://www.efinancialmodels.com/

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (21 preceding siblings ...)
  2021-08-27 17:52 ` ribevi6798 at enamelme dot com
@ 2021-08-28 18:31 ` buranlevent at yahoo dot com
  2021-09-06  9:10 ` focixujo at livinginsurance dot co.uk
                   ` (16 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: buranlevent at yahoo dot com @ 2021-08-28 18:31 UTC (permalink / raw)
  To: gdb-prs

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

Buran Levent <buranlevent at yahoo dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |buranlevent at yahoo dot com

--- Comment #23 from Buran Levent <buranlevent at yahoo dot com> ---
https://cars-scanner.fi/
https://cars-scanner.com.au/
https://gazette.com.ua/
https://dailyday.com.ua/
https://heavy.news/
https://labastide-saint-pierre.com/
https://word-press.info/
https://200iso.fr/
http://metro-montreal.com/
https://www.subsaharandrilling.com/
https://chanterelle.net/
https://netsolution.fr/
https://www.checkergooglerank.com/
https://bibliothequeparis.fr/
https://abripiscines.fr/
https://blague-courte.com/
https://defisconseil.fr/
https://www.justin-timberlake.net/
https://seo-consult.fr/
https://blur.fr/
http://www.websiteseo.biz/
https://creation-logo.org/
http://web-directory.net/
https://thebusinessdaily.org/
https://shespeaks.ca/
https://e-radio.ca/
https://earnwithsocial.ca/
https://3km.ca/
https://freshhive.ca/
https://thenewsowl.com/
https://canadianreporter.ca/
https://yoursavings.ca/
https://news.insightinteractive.ca/
https://spotlightmagazine.ca/
https://boutique.chateausaintlouis.fr/fr/
https://www.guidebogota.com/
https://google-adsense.info/
https://www.websiteworth.biz/
https://www.jobsfinder.biz/
https://www.tastytables.net/
http://wikichers.com/
https://www.checkergooglerank.com/
https://www.maxicar31.com/
http://www.commission-de-surendettement.fr/
https://audi-toulouse.fr/
https://taipan.fr/
http://taillehaie.fr/
https://lose-weight-fast.org/
https://dreamweaver.fr/
https://dictons.fr/
https://besthotels.hamburg/
https://fuuei-fukuoka.com/
http://fichiers.biz/
https://reseauxsociaux.info/
https://siteinternet.org/
https://ski-alpin.fr/
http://url-shortener.org/
https://neomail.fr/

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (22 preceding siblings ...)
  2021-08-28 18:31 ` buranlevent at yahoo dot com
@ 2021-09-06  9:10 ` focixujo at livinginsurance dot co.uk
  2021-09-10 19:40 ` mehmetgelisin at aol dot com
                   ` (15 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: focixujo at livinginsurance dot co.uk @ 2021-09-06  9:10 UTC (permalink / raw)
  To: gdb-prs

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

james robin <focixujo at livinginsurance dot co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |focixujo at livinginsurance dot co
                   |                            |.uk

--- Comment #24 from james robin <focixujo at livinginsurance dot co.uk> ---
https://www.montgomeryasphalt.com/
https://www.orangeasphaltrepair.com/
https://www.stpaulasphalt.com/
https://www.miamiflcarpentry.com/
https://www.carpentryatl.com/
https://www.sanbernardinocarpetcleaning.com/
https://www.carpetcleaningfontanaca.com/
https://www.cincinnaticarpetcleaner.net/
https://www.stocktoncarpetcleaning.net/
https://www.carpetsbakersfield.com/
https://www.carpetswestminster.com/
https://www.grandrapidscarpets.com/
https://www.alexandriavacarpet.com/
https://www.colacarpetcleaning.com/
https://www.carpetcleaningvabeach.com/
https://www.newportnewscarpetcleaning.com/
https://www.chimneycleanrepair.com/
https://www.fremontconcrete.net/
https://www.visaliaconcrete.net/
https://www.murrietacaconcrete.com/
https://www.jolietconcrete.net/
https://www.friscoconcrete.net/
https://www.wichitadatacabling.com/
https://www.atldatacabling.com/
https://www.datacablingmiami.com/
https://www.columbiascdeckbuilder.com/
https://www.tallahasseedeckbuilder.com/
https://www.clarksvilledeckbuilder.net/
https://www.alexandriadeckbuilder.com/
https://www.norfolkdeckbuilder.com/
https://www.athensdeckbuilder.com/
https://www.napervilledeckbuilder.com/
https://www.slcdeckbuilder.com/
https://www.centennialdeckbuilder.com/
https://www.kansascitydeck.builder/
https://www.springfielddeckbuilder.com/
https://augustadeckbuilder.com/
https://www.brownsvilledeckbuilder.com/
https://www.dentondeckbuilder.com/
https://www.worcesterdeckbuilder.com/
https://www.mckinneydeck.builder/
https://www.lowelldeckbuilder.com/
https://www.vancouverdeckbuilder.net/
https://www.cambridgedeckbuilder.com/
https://www.columbiamodeckbuilder.com/
https://www.pearlanddeckbuilder.com/
https://www.lakelanddeckbuilder.com/
https://www.westjordandeck.builder/
https://www.bellevuedeckbuilder.com/
https://www.pembrokepinesdeck.builder/
https://www.scottsdaledisabilitylawyer.com/
https://www.divorcescottsdaleaz.com/
https://www.epoxyflooringspokane.com/
https://www.norfolkepoxyflooring.com/
https://www.morenovalleyepoxy.com/
https://www.palmdalecapainters.com/
https://www.paintersgrandprairie.com/
https://www.modestofencebuilder.com/
https://www.glendalefencebuilder.com/
https://www.gilbertfencebuilder.com/
https://www.fontanafencebuilder.com/
https://www.irvingfencebuilder.com/
https://www.morenovalleyfence.net/
https://www.boisefencebuilder.com/
https://www.mesafence.net/
https://www.glendalefence.net/
https://www.honolulufence.net/
https://www.columbiamocontractor.net/
https://www.newhavencontractor.net/
https://www.miamiflcontractor.com/
https://www.ranchocucamongacontractor.net/
https://www.richmondgutter.net/
https://www.desmoinesgutter.com/
https://www.garlandtxpainters.com/
https://www.norfolkinteriorpainters.com/
https://www.atllocksmithga.com/
https://www.locksmithsscottsdale.com/
https://www.tampamasonry.net/
https://www.ontariomasonry.net/
https://www.stamfordmasonry.net/
https://www.gardengrovemasonry.net/
https://www.sterlingheightsmasonry.net/
https://www.newhavenmasonry.net/
https://www.scottsdaleprivateeye.com/
https://www.miamiflprivateinvestigator.com/
https://www.privateeyecincinnati.com/
https://www.kentremodeling.net/
https://www.kckremodeling.com/
https://www.allenremodeling.net/
https://www.orlandoremodeling.net/
https://www.sealcoatingkansascity.com/
https://www.sealcoatcoloradosprings.com/
https://www.elginilsealcoating.com/
https://www.providencesealcoating.com/
https://www.stpaulsealcoating.com/
https://www.tampaflsealcoating.com/
https://www.atlsealcoating.com/
https://www.sanbernardinosealcoating.com/
https://www.elginsepticservices.com/
https://www.aurorasepticservices.com/
https://www.fontanasepticservices.com/
https://www.sanbernardinosepticservices.com/
https://www.minneapolisstuccorepair.com/
https://www.stuccorepairorlandofl.com/
https://www.stuccorepaircapecoral.com/
https://www.orlandofltowing.com/
https://www.ftlauderdaletreeremoval.net/
https://www.treeservicefremont.net/
https://www.treeserviceanaheim.net/
https://www.treeservicestockton.net/
https://www.cincinnatitreecare.net/
https://www.tempetreeservice.net/
https://www.treeserviceaurora.net/
https://www.treeservicebrownsville.com/
https://www.lakewoodtreeservice.net/
https://www.newhaventreeservice.net/
https://www.montgomerytreeservice.net/
https://www.lansingtreecare.net/
https://www.tuscaloosatreeservice.net/
https://www.shreveportreeservice.com/
https://www.batonrougetreeservice.net/
https://www.davenporttreeservice.net/
https://www.greeleytreeservice.net/
https://www.stocktonweddingplanner.com/
https://www.pasadenatxsealcoating.com/

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (23 preceding siblings ...)
  2021-09-06  9:10 ` focixujo at livinginsurance dot co.uk
@ 2021-09-10 19:40 ` mehmetgelisin at aol dot com
  2021-09-14 17:29 ` johnb6174 at gmail dot com
                   ` (14 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: mehmetgelisin at aol dot com @ 2021-09-10 19:40 UTC (permalink / raw)
  To: gdb-prs

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

Mehmet gelisin <mehmetgelisin at aol dot com> changed:

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

--- Comment #25 from Mehmet gelisin <mehmetgelisin at aol dot com> ---
outputs/gdb.fortran/function-calls/function-calls \
  -ex "break 241" \
  -ex "run" \
  -ex "p c_nd" \ http://www-look-4.com/
  -ex "p derived_types_and_module_calls::pass_cart_nd(c_nd)"
+break 241
Breakpoint 1 at 0x4018bc: file function-calls.f90, line 241.
+run
             (2.09999990,3.29999995) http://www.compilatori.com/
           4           5
          23
             (2.09999990,3.29999995)
   3.40000010     http://www.wearelondonmade.com/
           6


Breakpoint 1, function_calls () at function-calls.f90:241
241         deallocate(c_nd%d) ! post_init http://www.jopspeech.com/
+p c_nd
Cannot access memory at address 0x4
+p derived_types_and_module_calls::pass_cart_nd(c_nd) http://joerg.li/

Program received signal SIGSEGV, Segmentation fault. 
0x0000000000400f93 in derived_types_and_module_calls::pass_cart_nd (c=<error
reading variable: Cannot access memory at address 0xc>) at http://connstr.net/ 
/home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.fortran/function-calls.f90:130
http://embermanchester.uk/ 
130             pass_cart_nd = ubound(c%d,1,4)
The program being debugged was signaled while in a function called from GDB.
GDB remains in the frame where the signal was received.
http://www.slipstone.co.uk/ 
To change this behavior use "set unwindonsignal on".
Evaluation of the expression containing the function
(derived_types_and_module_calls::pass_cart_nd) will be abandoned.
http://www.logoarts.co.uk/ 

5b6d1e4fa4fc:

$ ./binutils-gdb/gdb/gdb --data-directory binutils-gdb/gdb/data-directory
-batch a.out -ex "b puts" -ex "r" -ex "bt"
Breakpoint 1 at 0x1021a0 http://www.acpirateradio.co.uk/ 

Breakpoint 1, 0xffff80010019c63c in puts () from
/lib/sparc64-linux-gnu/libc.so.6
#0  0xffff80010019c63c in puts () from /lib/sparc64-linux-gnu/libc.so.6
#1  0x000007feffdee2d9 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

At 5b6d1e4fa4fc^: https://waytowhatsnext.com/

./binutils-gdb/gdb/gdb --data-directory binutils-gdb/gdb/data-directory -batch
a.out -ex "b puts" -ex "r" -ex "bt"
Breakpoint 1 at 0x1021a0

Breakpoint 1, 0xffff80010019c63c in puts () from
/lib/sparc64-linux-gnu/libc.so.6 https://www.webb-dev.co.uk/ 
#0  0xffff80010019c63c in puts () from /lib/sparc64-linux-gnu/libc.so.6
#1  0x00000100000007f8 in hello () at test.c:4
#2  0x0000010000000810 in main () at test.c:8
 http://www.iu-bloomington.com/ 
Since this is a 9 -> 10 regression, I'll mark it with the 10.2 milestone.  I
don't plan to look more into it at the moment.

Note: I tried to generate a core file, to be able to analyze further on my
local machine, but I wasn't able to load it.  GDB doesn't find the

5b6d1e4fa4fc:

$ ./binutils-gdb/gdb/gdb --data-directory binutils-gdb/gdb/data-directory
-batch a.out -ex "b puts" -ex "r" -ex "bt"
Breakpoint 1 at 0x1021a0 

Breakpoint 1, 0xffff80010019c63c in puts () from
/lib/sparc64-linux-gnu/libc.so.6
#0  0xffff80010019c63c in puts () from /lib/sparc64-linux-gnu/libc.so.6
#1  0x000007feffdee2d9 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

At 5b6d1e4fa4fc^: https://komiya-dental.com/

./binutils-gdb/gdb/gdb --data-directory binutils-gdb/gdb/data-directory -batch
a.out -ex "b puts" -ex "r" -ex "bt"
Breakpoint 1 at 0x1021a0

Breakpoint 1, 0xffff80010019c63c in puts () from
/lib/sparc64-linux-gnu/libc.so.6
#0  0xffff80010019c63c in puts () from /lib/sparc64-linux-gnu/libc.so.6
#1  0x00000100000007f8 in hello () at test.c:4
#2  0x0000010000000810 in main () at test.c:8

Since this is a 9 -> 10 regression, I'll mark it with the 10.2 milestone.  I
don't plan to look more into it at the moment.

Note: I tried to generate a core file, to be able to analyze further on my
local machine, but I wasn't able to load it.  GDB doesn't find the

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (24 preceding siblings ...)
  2021-09-10 19:40 ` mehmetgelisin at aol dot com
@ 2021-09-14 17:29 ` johnb6174 at gmail dot com
  2021-09-14 18:48 ` mark at klomp dot org
                   ` (13 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: johnb6174 at gmail dot com @ 2021-09-14 17:29 UTC (permalink / raw)
  To: gdb-prs

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

johnb6174 <johnb6174 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |johnb6174 at gmail dot com

--- Comment #26 from johnb6174 <johnb6174 at gmail dot com> ---
useful information on topics that plenty are interested on for this wonderful
post.Admiring the time and effort you put into your
b!..https://abbicare.com.au/
https://www.miningbusiness.net/
https://getweightfast.com

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (25 preceding siblings ...)
  2021-09-14 17:29 ` johnb6174 at gmail dot com
@ 2021-09-14 18:48 ` mark at klomp dot org
  2021-09-26 13:31 ` tes.vik1986 at gmail dot com
                   ` (12 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: mark at klomp dot org @ 2021-09-14 18:48 UTC (permalink / raw)
  To: gdb-prs

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

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at klomp dot org

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (26 preceding siblings ...)
  2021-09-14 18:48 ` mark at klomp dot org
@ 2021-09-26 13:31 ` tes.vik1986 at gmail dot com
  2021-10-09 11:00 ` gulsenenginar at aol dot com
                   ` (11 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: tes.vik1986 at gmail dot com @ 2021-09-26 13:31 UTC (permalink / raw)
  To: gdb-prs

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

Kylan <tes.vik1986 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tes.vik1986 at gmail dot com

--- Comment #27 from Kylan <tes.vik1986 at gmail dot com> ---
[gdb/breakpoints] Handle glibc with debuginfo in
create_exception_master_breakpoint
    https://komiya-dental.com/crypto/new-coins/
    The test-case nextoverthrow.exp is failing on targets with unstripped libc.

    This is a regression since commit 1940319c0ef "[gdb] Fix internal-error in
    process_event_stop_test". http://www-look-4.com/health/winter-sickness/

    The problem is that this code in create_exception_master_breakpoint:
    ... http://www.iu-bloomington.com/crypto/china-affect-on-crypto/
          for (objfile *sepdebug = obj->separate_debug_objfile;
               sepdebug != nullptr; sepdebug =
sepdebug->separate_debug_objfile)
            if (create_exception_master_breakpoint_hook (sepdebug))
    ... https://www.webb-dev.co.uk/crypto/crypto-fell/
    iterates over all the separate debug object files, but fails to handle the
    case that obj itself has the debug info we're looking for.
    https://waytowhatsnext.com/crypto/cryptocurrency-taxes/
    Fix this by using the separate_debug_objfiles () range instead, which does
    iterate both over obj and the obj->separate_debug_objfile chain.
    http://www.acpirateradio.co.uk/technology/facetime/
    Tested on x86_64-linux. [gdb/breakpoints] Handle glibc with debuginfo in
create_exception_master_breakpoint
    http://www.logoarts.co.uk/computers/printer-types/
    The test-case nextoverthrow.exp is failing on targets with unstripped libc.
    http://www.slipstone.co.uk/computers/isofix/
    This is a regression since commit 1940319c0ef "[gdb] Fix internal-error in
    process_event_stop_test". 
    http://embermanchester.uk/computers/video-conversation/
    The problem is that this code in create_exception_master_breakpoint:
    ... http://connstr.net/computers/chargers-tech/
          for (objfile *sepdebug = obj->separate_debug_objfile;
               sepdebug != nullptr; sepdebug =
sepdebug->separate_debug_objfile)
            if (create_exception_master_breakpoint_hook (sepdebug))
    ... http://joerg.li/health/xiaomi/
    iterates over all the separate debug object files, but fails to handle the
    case that obj itself has the debug info we're looking for.
    http://www.jopspeech.com/property/slim-pen-2/
    Fix this by using the separate_debug_objfiles () range instead, which does
    iterate both over obj and the obj->separate_debug_objfile chain.
    http://www.wearelondonmade.com/health/check-ups/
    Tested on x86_64-linux.
[gdb/breakpoints] Handle glibc with debuginfo in
create_exception_master_breakpoint
    http://www.compilatori.com/property/dark-mode/
    The test-case nextoverthrow.exp is failing on targets with unstripped libc.

    This is a regression since commit 1940319c0ef "[gdb] Fix internal-error in
    process_event_stop_test".

    The problem is that this code in create_exception_master_breakpoint:
    ... https://manta-termica.com/
https://shade-cloth.net/
https://trellis-netting.net/
https://invernavelo.net/
https://marijuana-netting.net/
https://gallinero.mx/
https://control-de-palomas.mx/
https://guacamalla.net/
          for (objfile *sepdebug = obj->separate_debug_objfile;
               sepdebug != nullptr; sepdebug =
sepdebug->separate_debug_objfile)
            if (create_exception_master_breakpoint_hook (sepdebug))
    ...
    iterates over all the separate debug object files, but fails to handle the
    case that obj itself has the debug info we're looking for.
https://scrog.mx/
https://cannabis-netting.net/
https://casa-sombra.mx/
https://ground-cover.mx/
https://hortomallas.es/
https://malla-espaldera.mx/
https://malla-pepinera.com/
https://malla-sombra.mx/

    Fix this by using the separate_debug_objfiles () range instead, which does
    iterate both over obj and the obj->separate_debug_objfile chain.

    Tested on x86_64-linux.
[gdb/breakpoints] Handle glibc with debuginfo in
create_exception_master_breakpoint
    https://www.hortomallas.com/en/grow-pumpkin-on-trellises-netting/
https://www.hortomallas.com/malla-plastica-para-jardin-canceles-vallas-rejas/
http://frost-fabric.net/
http://gancho-tutoreo-tenax.net/
http://flower-supports.net/
http://hail-protection-net.com/
https://www.hortomallas.net/
http://macro-tunel.com/
    The test-case nextoverthrow.exp is failing on targets with unstripped libc.

    This is a regression since commit 1940319c0ef "[gdb] Fix internal-error in
    process_event_stop_test".

    The problem is that this code in create_exception_master_breakpoint:
    ...
          for (objfile *sepdebug = obj->separate_debug_objfile;
               sepdebug != nullptr; sepdebug =
sepdebug->separate_debug_objfile)
            if (create_exception_master_breakpoint_hook (sepdebug))
    ... https://mohamie-jeddah.com/
https://www.beyandiet.com/
https://www.bebealis.com/
https://byothe.fr/
https://ns-communication.fr/
https://www.hortomallas.com/en/the-advantage-of-chicken-wire-mesh-with-hexagonal-netting/
https://www.hortomallas.com/en/how-tall-should-the-cucumber-trellis-height-be/
https://www.hortomallas.com/precio-la-tela-gallinera-bajo/
https://www.hortomallas.com/en/best-price-of-the-chicken-netting-save-money-with-chickenmalla/
https://www.hortomallas.com/en/tomato-cages/
https://www.hortomallas.com/en/product-category/privacy-and-windbreakers/polisombra-total-privacy/
    iterates over all the separate debug object files, but fails to handle the
    case that obj itself has the debug info we're looking for.

    Fix this by using the separate_debug_objfiles () range instead, which does
    iterate both over obj and the obj->separate_debug_objfile chain.

    Tested on x86_64-linux.
[gdb/breakpoints] Handle glibc with debuginfo in
create_exception_master_breakpoint

    The test-case nextoverthrow.exp is failing on targets with unstripped libc.

    This is a regression since commit 1940319c0ef "[gdb] Fix internal-error in
    process_event_stop_test". https://www.station-alexandre.com/
https://fintechzoom.com/lifestyle/entertainment/gaming/ro-ghoul/roblox-ro-ghoul-codes/
https://www.hunny-pool.com/
https://www.formations-continues.com/
https://nutrienta.co/
https://2macp.fr/
https://mymystore.online/
https://www.antiguachiamaitalia.it/
https://rattanmart.com/
https://bohemiansmart.com/

    The problem is that this code in create_exception_master_breakpoint:
    ...
          for (objfile *sepdebug = obj->separate_debug_objfile;
               sepdebug != nullptr; sepdebug =
sepdebug->separate_debug_objfile)
            if (create_exception_master_breakpoint_hook (sepdebug))
    ...
    iterates over all the separate debug object files, but fails to handle the
    case that obj itself has the debug info we're looking for.

    Fix this by using the separate_debug_objfiles () range instead, which does
    iterate both over obj and the obj->separate_debug_objfile chain.
https://mohamie-saudi.com/
https://fintechzoom.com/lifestyle/entertainment/gaming/rimworld/the-best-rimworld-mods/
https://www.nimblehand.com/
https://geoslam.xyz/
https://fintechzoom.com/lifestyle/entertainment/gaming/tower-defense-simulator/codes/
https://www.lafabriquedeslutins.fr/

    Tested on x86_64-linux.
[gdb/breakpoints] Handle glibc with debuginfo in
create_exception_master_breakpoint

    The test-case nextoverthrow.exp is failing on targets with unstripped libc.

    This is a regression since commit 1940319c0ef "[gdb] Fix internal-error in
    process_event_stop_test".

    The problem is that this code in create_exception_master_breakpoint:
    ...
          for (objfile *sepdebug = obj->separate_debug_objfile;
               sepdebug != nullptr; sepdebug =
sepdebug->separate_debug_objfile)
            if (create_exception_master_breakpoint_hook (sepdebug))
    ...
https://fintechzoom.com/lifestyle/entertainment/gaming/final-fantasy/ffxiv-classes-guide-on-final-fantasy-14-select-the-best-job/
https://www.mindrnd.com/
https://akoestiekopmaat.nl/
https://fintechzoom.com/lifestyle/entertainment/gaming/zombie-games-do-you-know-what-are-the-best-games-for-pc-in-2021/
https://www.cinogel.com/
    iterates over all the separate debug object files, but fails to handle the
    case that obj itself has the debug info we're looking for.

    Fix this by using the separate_debug_objfiles () range instead, which does
    iterate both over obj and the obj->separate_debug_objfile chain.

    Tested on x86_64-linux.

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (27 preceding siblings ...)
  2021-09-26 13:31 ` tes.vik1986 at gmail dot com
@ 2021-10-09 11:00 ` gulsenenginar at aol dot com
  2021-10-10 16:10 ` oficaj3 at gmail dot com
                   ` (10 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: gulsenenginar at aol dot com @ 2021-10-09 11:00 UTC (permalink / raw)
  To: gdb-prs

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

Gulsen Engin <gulsenenginar at aol dot com> changed:

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

--- Comment #28 from Gulsen Engin <gulsenenginar at aol dot com> ---
#0  compute_frame_id (fi=0x10007c50040) at
/home/simark/src/wt/good/gdb/frame.c:549
#1  0x000001000324ddd8 in get_prev_frame_if_no_cycle (this_frame=0x10007c4f230)
at /home/simark/src/wt/good/gdb/frame.c:1927
http://www-look-4.com/health/covid-and-tech/
#2  0x000001000324f9f8 in get_prev_frame_always_1 (this_frame=0x10007c4f230) at
/home/simark/src/wt/good/gdb/frame.c:2108
https://komiya-dental.com/property/google-android/
#3  0x000001000324fa38 in get_prev_frame_always (this_frame=0x10007c4f230) at
/home/simark/src/wt/good/gdb/frame.c:2124
http://www.iu-bloomington.com/shopping/hatchback-cars/
#4  0x00000100032511fc in get_prev_frame (this_frame=0x10007c4f230) at
/home/simark/src/wt/good/gdb/frame.c:2376
https://waytowhatsnext.com/sports/asian-sports/
#5  0x00000100042972c0 in backtrace_command_1 (fp_opts=..., bt_opts=...,
http://www.wearelondonmade.com/technology/van-technology/  count_exp=0x0,
from_tty=1) at /home/simark/src/wt/good/gdb/stack.c:2055
#6  0x0000010004297918 in backtrace_command (arg=0x0, from_tty=1) at
/home/simark/src/wt/good/gdb/stack.c:2183
http://www.jopspeech.com/travel/windows-11/
#7  0x0000010002a4a538 in do_const_cfunc (c=0x10007c93390, args=0x0,
from_tty=1) at /home/simark/src/wt/good/gdb/cli/cli-decode.c:107
http://joerg.li/health/covid-and-tech/
#8  0x0000010002a56ea4 in cmd_func (cmd=0x10007c93390, args=0x0, from_tty=1) at
/home/simark/src/wt/good/gdb/cli/cli-decode.c:1952
http://connstr.net/services/mobile-games/
#9  0x00000100045e32e4 in execute_command (p=0x10007ab9c52 "", from_tty=1) at
/home/simark/src/wt/good/gdb/top.c:653
http://embermanchester.uk/services/whatsapp-number-change/
#10 0x00000100031b21c0 in command_handler (command=0x10007ab9c50 "bt") at
/home/simark/src/wt/good/gdb/event-top.c:587
http://www.slipstone.co.uk/property/hp-of-cars/
#11 0x00000100031b2d4c in command_line_handler (rl=...) at
/home/simark/src/wt/good/gdb/event-top.c:772
http://www.logoarts.co.uk/travel/london/
#12 0x00000100031b06e4 in gdb_rl_callback_handler (rl=0x10007cc5e30 "bt") at
/home/simark/src/wt/good/gdb/event-top.c:218
#13 0x0000010004ae6410 in rl_callback_read_char () at
http://www.acpirateradio.co.uk/health/transportation-security/
/home/simark/src/wt/good/readline/readline/callback.c:281
#14 0x00000100031b02b0 in gdb_rl_callback_read_char_wrapper_noexcept () at
/home/simark/src/wt/good/gdb/event-top.c:176
http://www.compilatori.com/technology/download-videos/
#15 0x00000100031b03d4 in gdb_rl_callback_read_char_wrapper
(client_data=0x10007ab99c0) at /home/simark/src/wt/good/gdb/event-top.c:193
#16 0x00000100031b1a4c in stdin_event_handler (error=0,
client_data=0x10007ab99c0) at /home/simark/src/wt/good/gdb/event-top.c:515
https://www.webb-dev.co.uk/services/navona-trains/
#17 0x00000100031aa778 in handle_file_event (file_ptr=0x10007d6aa20,
ready_mask=1) at /home/simark/src/wt/good/gdb/event-loop.c:731
#18 0x00000100031ab3e0 in gdb_wait_for_event (block=1) at 


https://pro-sangyoui.com/
https://fintechzoom.com/reviews/15-best-water-bottles-of-2021/
https://fintechzoom.com/reviews/10-best-yoga-mats-of-2021/
https://wikifinancepedia.com/
https://financeplusinsurance.com/
https://financeinsuranceblog.com/
https://fintechzoom.com/reviews/the-greatest-robot-vacuums-for-assure-cleaner-floors/
https://fintechzoom.com/reviews/the-11-best-air-purifiers-in-2021/
https://fintechzoom.com/reviews/the-6-best-cordless-stick-vacuum-in-2021/
https://amazon.com/Christopher-Horne/e/B08D6C1D2P%3Fref=dbs_a_mng_rwt_scns_share
https://nhacai888b.com/
https://www.soicau888.net/
https://kaiyokukan.vn/
http://twin688.net/
https://typhu88.me/
https://fitveform.com/
https://www.thegamblinggurus.com/
https://nodepositpokeronline.com/
https://onlinecasinoku.com/
https://slickcashloanca.blogspot.com/
https://www.aaz-credit-immobilier.com/
https://www.sport-trader.com/
https://www.lespersiennes.com/
https://www.espresso-international.it/
https://www.espresso-international.fi/
https://footballexpress.in/latest-news/
https://sixsports.in/category/f1-racing/
https://true-tech.net/ttstore
https://www.alivechristians.com/bible-verses-about-healing-sickness/
https://photoslate.co/
https://trellising-net.com/
https://www.seminariostop.com/seminarios-y-talleres/como-importar-de-china-alibaba-aliexpress-dropshipping-peru/
https://bestonlinegambler.com/
https://vipcasinotips.com/
https://casinogamblingideas.com/
https://realmoneycasinoguides.com/
https://casinoexpertadvice.com/
https://komopoker5.com/
https://zehabesha.com/

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (28 preceding siblings ...)
  2021-10-09 11:00 ` gulsenenginar at aol dot com
@ 2021-10-10 16:10 ` oficaj3 at gmail dot com
  2021-10-19  7:14 ` progonsaytu at gmail dot com
                   ` (9 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: oficaj3 at gmail dot com @ 2021-10-10 16:10 UTC (permalink / raw)
  To: gdb-prs

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

oficaj3 at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |oficaj3 at gmail dot com

--- Comment #29 from oficaj3 at gmail dot com ---
https://www.adhan.ru/archives/19750
https://www.adhan.ru/archives/19749
https://www.adhan.ru/archives/19087
https://www.adhan.ru/archives/18343
https://www.adhan.ru/archives/19372
https://www.adhan.ru/archives/18337
https://www.adhan.ru/archives/19069
https://www.adhan.ru/archives/18335
https://www.adhan.ru/archives/20345
https://www.adhan.ru/archives/19818
https://www.adhan.ru/archives/19748
https://www.adhan.ru/archives/19371
https://www.adhan.ru/archives/19370
https://www.adhan.ru/archives/20344
https://www.adhan.ru/archives/19369
https://www.adhan.ru/archives/18319
https://www.adhan.ru/archives/19712
https://www.adhan.ru/archives/19711
https://www.adhan.ru/archives/18833
https://www.adhan.ru/archives/18825
https://www.adhan.ru/archives/18823
https://www.adhan.ru/archives/19747
https://www.adhan.ru/archives/18818
https://www.adhan.ru/archives/18810
https://www.adhan.ru/archives/18806
https://www.adhan.ru/archives/18315
https://www.adhan.ru/archives/19710
https://www.adhan.ru/archives/19817
https://www.adhan.ru/archives/18313
https://www.adhan.ru/archives/20343
https://www.adhan.ru/archives/19031
https://www.adhan.ru/archives/19030
https://www.adhan.ru/archives/18575
https://www.adhan.ru/archives/20342
https://www.adhan.ru/archives/20341
https://www.adhan.ru/archives/17622
https://www.adhan.ru/archives/17620
https://www.adhan.ru/archives/17618
https://www.adhan.ru/archives/17607
https://www.adhan.ru/archives/17605
https://www.adhan.ru/archives/20340
https://www.adhan.ru/archives/20339
https://www.adhan.ru/archives/20338
https://www.adhan.ru/archives/18269
https://www.adhan.ru/archives/18265
https://www.adhan.ru/archives/18263
https://www.adhan.ru/archives/18261
https://www.adhan.ru/archives/18259
https://www.adhan.ru/archives/20337
https://www.adhan.ru/archives/20336
https://www.adhan.ru/archives/19365
https://www.adhan.ru/archives/20335
https://www.adhan.ru/archives/20334
https://www.adhan.ru/archives/20333
https://www.adhan.ru/archives/18190
https://www.adhan.ru/archives/19061
https://www.adhan.ru/archives/18681
https://www.adhan.ru/archives/18196
https://www.adhan.ru/archives/18678
https://www.adhan.ru/archives/20332
https://www.adhan.ru/archives/18661
https://www.adhan.ru/archives/18181
https://www.adhan.ru/archives/20331
https://www.adhan.ru/archives/19364
https://www.adhan.ru/archives/18122
https://www.adhan.ru/archives/20330
https://www.adhan.ru/archives/19363
https://www.adhan.ru/archives/20329
https://www.adhan.ru/archives/18079
https://www.adhan.ru/archives/18108

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (29 preceding siblings ...)
  2021-10-10 16:10 ` oficaj3 at gmail dot com
@ 2021-10-19  7:14 ` progonsaytu at gmail dot com
  2021-10-23 13:46 ` fiteva5725 at bomoads dot com
                   ` (8 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: progonsaytu at gmail dot com @ 2021-10-19  7:14 UTC (permalink / raw)
  To: gdb-prs

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

progonsaytu <progonsaytu at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |progonsaytu at gmail dot com

--- Comment #30 from progonsaytu <progonsaytu at gmail dot com> ---
https://www.ремонты-квартир.com/
https://www.дизайн-квартиры.com/
https://www.о-ремонте.com/
https://www.о-заборах.com/
https://www.bsegypt.com/
https://www.buyingrealty.net/
https://www.khersonnews.com/
https://www.kontrolstroy.info/
https://www.sama-mama.com/
https://www.secretovnet.org/
https://www.teleriko.com/
https://www.us-best-store.com/
https://www.віктор.com/
https://www.accord-hotel.ru/
https://releazer.ru/
https://www.a-n-e-k-d-o-t.ru/
https://www.adhan.ru/
http://www.al-aures.ru/
https://www.apriori-design.ru/
http://artdoski.ru/
https://www.bombusmod.net.ru/
https://www.canadianahealthandcaremallreviews.ru/
https://www.celestiaproject.ru/
https://www.cryptogu.ru/
https://www.downloadskypefree.ru/
https://www.encyclopedia-flowers.ru/
https://www.factura.net.ru/
http://freewizards.ru/
http://futurefactory.ru/
https://glina-med.ru/
http://google-dmoz.ru/
http://iix.su/
https://www.imperia51.ru/
https://www.info-tehnologii.ru/
https://www.kvartira-v-bolgarii.ru/
https://ljubi-i-pozdravljaj.ru/
https://www.majesticarticles.ru/
https://www.onlinecredit247.ru/
https://www.orfey.net.ru/
https://www.pgpk.net.ru/
https://www.rainbow.net.ru/
http://www.rainbowbaby.ru/
http://www.respublika-okon.ru/
https://ribku-lovim.ru/
http://rusorchestra.ru/
http://shmoscow.ru/
https://www.skifspb.ru/
https://www.spare.net.ru/
https://www.stranainform.ru/
https://www.taxi-smile.ru/
https://www.tkanishik.ru/
http://www.tremulous.net.ru/
https://trust-women.ru/
http://uralbel.ru/
https://www.yar-art-union.ru/
https://www.xn----7sbcngq4awkg0k.xn--p1ai/
https://www.xn----7sbbmgbytlh3a0ll.xn--p1ai/
https://www.xn--35-mlcuxidl.xn--p1ai/
https://www.xn--f1addf1alkk1d.xn--p1ai/
https://www.history-of-great-discoveries.com/
https://www.it-business-trends.com
https://www.interesting-history-of-art.com
https://www.interesting-news-about-cars.com
https://www.architecture-and-design-news.com
https://history-of-great-discoveries.blogspot.com/
https://it-business-trends.blogspot.com/
https://interesting-history-of-art.blogspot.com/
https://interesting-news-about-cars.blogspot.com/
https://architecture-and-design-news.blogspot.com/
https://www.secretovnet.org/archives/18806 
https://www.secretovnet.org/archives/17685 
https://www.secretovnet.org/archives/17683 
https://www.secretovnet.org/archives / 17681 
https://www.secretovnet.org/archives/13740 
https://www.secretovnet.org/archives/13737 
https://www.secretovnet.org/archives/13734 
https://www.secretovnet.org / archives / 13732 
https://www.secretovnet.org/archives/13729 
https://www.secretovnet.org/archives/17679 
https://www.secretovnet.org/archives/17677 
https://www.secretovnet .org / archives / 17675 
https://www.secretovnet.org/archives/17670 
https://www.secretovnet.org/archives/17667 
https://www.secretovnet.org/archives/18686
https://www.secretovnet.org/archives/18684 
https://www.secretovnet.org/archives/18682 
https://www.secretovnet.org/archives/17665 
https://www.secretovnet.org/archives / 17663 
https://www.secretovnet.org/archives/17661 
https://www.secretovnet.org/archives/17659 
https://www.secretovnet.org/archives/17657 
https://www.secretovnet.org / archives / 13723 
https://www.secretovnet.org/archives/13717 
https://www.secretovnet.org/archives/13714 
https://www.secretovnet.org/archives/13711 
https://www.secretovnet .org / archives / 13708 
https://www.secretovnet.org/archives/17655 
https://www.secretovnet.org/archives/13702 
https://www.secretovnet.org/archives/17647
https://www.secretovnet.org/archives/17645

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (30 preceding siblings ...)
  2021-10-19  7:14 ` progonsaytu at gmail dot com
@ 2021-10-23 13:46 ` fiteva5725 at bomoads dot com
  2021-10-24 10:02 ` glassmtech at ukr dot net
                   ` (7 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: fiteva5725 at bomoads dot com @ 2021-10-23 13:46 UTC (permalink / raw)
  To: gdb-prs

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

fiteva <fiteva5725 at bomoads dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fiteva5725 at bomoads dot com

--- Comment #31 from fiteva <fiteva5725 at bomoads dot com> ---
Thanks so much for sharing this awesome info! I am looking forward to see more
posts by you!
https://www.neuzeitwerber.de/

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (31 preceding siblings ...)
  2021-10-23 13:46 ` fiteva5725 at bomoads dot com
@ 2021-10-24 10:02 ` glassmtech at ukr dot net
  2021-10-29 10:57 ` kimolsun2020 at outlook dot com
                   ` (6 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: glassmtech at ukr dot net @ 2021-10-24 10:02 UTC (permalink / raw)
  To: gdb-prs

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

glassmtech <glassmtech at ukr dot net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |glassmtech at ukr dot net

--- Comment #32 from glassmtech <glassmtech at ukr dot net> ---
http://www.ремонты-квартир.com/
http://www.дизайн-квартиры.com/
http://www.о-ремонте.com/
http://www.о-заборах.com/
http://www.bsegypt.com/
http://www.buyingrealty.net/
http://www.khersonnews.com/
http://www.kontrolstroy.info/
http://www.sama-mama.com/
http://www.secretovnet.org/
http://www.teleriko.com/
http://www.us-best-store.com/
http://www.віктор.com/
http://www.accord-hotel.ru/
http://releazer.ru/
http://www.a-n-e-k-d-o-t.ru/
http://www.adhan.ru/
https://www.al-aures.ru/
http://www.apriori-design.ru/
https://artdoski.ru/
http://www.bombusmod.net.ru/
http://www.canadianahealthandcaremallreviews.ru/
http://www.celestiaproject.ru/
http://www.cryptogu.ru/
http://www.downloadskypefree.ru/
http://www.encyclopedia-flowers.ru/
http://www.factura.net.ru/
https://freewizards.ru/
https://futurefactory.ru/
http://glina-med.ru/
https://google-dmoz.ru/
https://iix.su/
http://www.imperia51.ru/
http://www.info-tehnologii.ru/
http://www.kvartira-v-bolgarii.ru/
http://ljubi-i-pozdravljaj.ru/
http://www.majesticarticles.ru/
http://www.onlinecredit247.ru/
http://www.orfey.net.ru/
http://www.pgpk.net.ru/
http://www.rainbow.net.ru/
https://www.rainbowbaby.ru/
https://www.respublika-okon.ru/
http://ribku-lovim.ru/
https://rusorchestra.ru/
https://shmoscow.ru/
http://www.skifspb.ru/
http://www.spare.net.ru/
http://www.stranainform.ru/
http://www.taxi-smile.ru/
http://www.tkanishik.ru/
https://www.tremulous.net.ru/
http://trust-women.ru/
https://uralbel.ru/
http://www.yar-art-union.ru/
http://www.xn----7sbcngq4awkg0k.xn--p1ai/
http://www.xn----7sbbmgbytlh3a0ll.xn--p1ai/
http://www.xn--35-mlcuxidl.xn--p1ai/
http://www.xn--f1addf1alkk1d.xn--p1ai/
http://www.history-of-great-discoveries.com/
http://www.it-business-trends.com
http://www.interesting-history-of-art.com
http://www.interesting-news-about-cars.com
http://www.architecture-and-design-news.com
https://ремонты-квартир.com/
https://дизайн-квартиры.com/
https://о-ремонте.com/
https://о-заборах.com/
https://bsegypt.com/
https://buyingrealty.net/
https://khersonnews.com/
https://kontrolstroy.info/
https://sama-mama.com/
https://secretovnet.org/
https://teleriko.com/
https://us-best-store.com/
https://віктор.com/
https://accord-hotel.ru/
https://www.releazer.ru/
https://a-n-e-k-d-o-t.ru/
https://adhan.ru/
http://al-aures.ru/
https://apriori-design.ru/
http://www.artdoski.ru/
https://bombusmod.net.ru/
https://canadianahealthandcaremallreviews.ru/
https://celestiaproject.ru/
https://cryptogu.ru/
https://downloadskypefree.ru/
https://encyclopedia-flowers.ru/
https://factura.net.ru/
http://www.freewizards.ru/
http://www.futurefactory.ru/
https://www.glina-med.ru/
http://www.google-dmoz.ru/
http://www.iix.su/
https://imperia51.ru/
https://info-tehnologii.ru/
https://kvartira-v-bolgarii.ru/
https://www.ljubi-i-pozdravljaj.ru/
https://majesticarticles.ru/
https://onlinecredit247.ru/
https://orfey.net.ru/
https://pgpk.net.ru/
https://rainbow.net.ru/
http://rainbowbaby.ru/
http://respublika-okon.ru/
https://www.ribku-lovim.ru/
http://www.rusorchestra.ru/
http://www.shmoscow.ru/
https://skifspb.ru/
https://spare.net.ru/
https://stranainform.ru/
https://taxi-smile.ru/
https://tkanishik.ru/
http://tremulous.net.ru/
https://www.trust-women.ru/
http://www.uralbel.ru/
https://yar-art-union.ru/
https://xn----7sbcngq4awkg0k.xn--p1ai/
https://xn----7sbbmgbytlh3a0ll.xn--p1ai/
https://xn--35-mlcuxidl.xn--p1ai/
https://xn--f1addf1alkk1d.xn--p1ai/
https://history-of-great-discoveries.com/
https://it-business-trends.com
https://interesting-history-of-art.com
https://interesting-news-about-cars.com
https://architecture-and-design-news.com

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (32 preceding siblings ...)
  2021-10-24 10:02 ` glassmtech at ukr dot net
@ 2021-10-29 10:57 ` kimolsun2020 at outlook dot com
  2021-10-29 12:07 ` huracantili20 at gmail dot com
                   ` (5 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: kimolsun2020 at outlook dot com @ 2021-10-29 10:57 UTC (permalink / raw)
  To: gdb-prs

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

Kuka Kim <kimolsun2020 at outlook dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kimolsun2020 at outlook dot com

--- Comment #33 from Kuka Kim <kimolsun2020 at outlook dot com> ---
https://fintechzoom.com/lifestyle/tech/login/godaddy-email-login/
https://fintechzoom.com/lifestyle/tech/login/telstra-bigpond-webmail-login-the-simple-guide-for-you/
https://gatewit.com/concursos-publicos/
https://www.hensachi-ranking.com/
Expected result (from GDB 9.2):
#0  0x0000000000108de4 in puts ()
#1  0x0000000000100950 in hello () at gdb-test.c:4
#2  0x0000000000100968 in main () at gdb-test.c:8


http://fishingnewsletters.co.uk/
Expected result (from GDB 9.2):
#0  0x0000000000108de4 in puts ()
#1  0x0000000000100950 in hello () at gdb-test.c:4
#2  0x0000000000100968 in main () at gdb-test.c:8

http://www.go-mk-websites.co.uk/
Expected result (from GDB 9.2):
#0  0x0000000000108de4 in puts ()
#1  0x0000000000100950 in hello () at gdb-test.c:4
#2  0x0000000000100968 in main () at gdb-test.c:8

http://www.mconstantine.co.uk/
Expected result (from GDB 9.2):
#0  0x0000000000108de4 in puts ()
#1  0x0000000000100950 in hello () at gdb-test.c:4
#2  0x0000000000100968 in main () at gdb-test.c:8

http://the-hunters.org/  Expected result (from GDB 9.2):
#0  0x0000000000108de4 in puts ()
#1  0x0000000000100950 in hello () at gdb-test.c:4
#2  0x0000000000100968 in main () at gdb-test.c:8

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (33 preceding siblings ...)
  2021-10-29 10:57 ` kimolsun2020 at outlook dot com
@ 2021-10-29 12:07 ` huracantili20 at gmail dot com
  2021-11-02 15:21 ` gepaw63633 at dukeoo dot com
                   ` (4 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: huracantili20 at gmail dot com @ 2021-10-29 12:07 UTC (permalink / raw)
  To: gdb-prs

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

Huracan <huracantili20 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |huracantili20 at gmail dot com

--- Comment #34 from Huracan <huracantili20 at gmail dot com> ---
https://fintechzoom.com/lifestyle/tech/login/godaddy-email-login/
https://fintechzoom.com/lifestyle/tech/login/telstra-bigpond-webmail-login-the-simple-guide-for-you/
https://gatewit.com/concursos-publicos/
https://www.hensachi-ranking.com/
Expected result (from GDB 9.2):
#0  0x0000000000108de4 in puts ()
#1  0x0000000000100950 in hello () at gdb-test.c:4
#2  0x0000000000100968 in main () at gdb-test.c:8


http://fishingnewsletters.co.uk/
Expected result (from GDB 9.2):
#0  0x0000000000108de4 in puts ()
#1  0x0000000000100950 in hello () at gdb-test.c:4
#2  0x0000000000100968 in main () at gdb-test.c:8

http://www.go-mk-websites.co.uk/
Expected result (from GDB 9.2):
#0  0x0000000000108de4 in puts ()
#1  0x0000000000100950 in hello () at gdb-test.c:4
#2  0x0000000000100968 in main () at gdb-test.c:8

http://www.mconstantine.co.uk/
Expected result (from GDB 9.2):
#0  0x0000000000108de4 in puts ()
#1  0x0000000000100950 in hello () at gdb-test.c:4
#2  0x0000000000100968 in main () at gdb-test.c:8

http://the-hunters.org/  Expected result (from GDB 9.2):
#0  0x0000000000108de4 in puts ()
#1  0x0000000000100950 in hello () at gdb-test.c:4
#2  0x0000000000100968 in main () at gdb-test.c:8

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (34 preceding siblings ...)
  2021-10-29 12:07 ` huracantili20 at gmail dot com
@ 2021-11-02 15:21 ` gepaw63633 at dukeoo dot com
  2021-11-06 21:12 ` paneki8601 at dukeoo dot com
                   ` (3 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: gepaw63633 at dukeoo dot com @ 2021-11-02 15:21 UTC (permalink / raw)
  To: gdb-prs

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

gepaw <gepaw63633 at dukeoo dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gepaw63633 at dukeoo dot com

--- Comment #35 from gepaw <gepaw63633 at dukeoo dot com> ---
Nice blog and absolutely outstanding. You can do something much better but i
still say this perfect.Keep trying for the best.
https://meridianplumbing.co.uk

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (35 preceding siblings ...)
  2021-11-02 15:21 ` gepaw63633 at dukeoo dot com
@ 2021-11-06 21:12 ` paneki8601 at dukeoo dot com
  2021-11-16 19:05 ` xecana8007 at funboxcn dot com
                   ` (2 subsequent siblings)
  39 siblings, 0 replies; 41+ messages in thread
From: paneki8601 at dukeoo dot com @ 2021-11-06 21:12 UTC (permalink / raw)
  To: gdb-prs

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

paneki <paneki8601 at dukeoo dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |paneki8601 at dukeoo dot com

--- Comment #36 from paneki <paneki8601 at dukeoo dot com> ---
Awesome article!  I want people to know just how good this information is in
your article.  It’s interesting, compelling content.  Your views are much like
my own concerning this subject.
https://www.jltstore.com/

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (36 preceding siblings ...)
  2021-11-06 21:12 ` paneki8601 at dukeoo dot com
@ 2021-11-16 19:05 ` xecana8007 at funboxcn dot com
  2021-11-16 19:08 ` xecana8007 at funboxcn dot com
  2021-11-22  7:37 ` gexed96894 at keagenan dot com
  39 siblings, 0 replies; 41+ messages in thread
From: xecana8007 at funboxcn dot com @ 2021-11-16 19:05 UTC (permalink / raw)
  To: gdb-prs

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

tesaso8237 at funboxcn dot comxecana8007@funboxcn.com <xecana8007 at funboxcn dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xecana8007 at funboxcn dot com

--- Comment #37 from tesaso8237 at funboxcn dot comxecana8007@funboxcn.com <xecana8007 at funboxcn dot com> ---
Your blog provided us with valuable information to work with. Each & every tips
of your post are awesome. Thanks a lot for sharing. Keep blogging.. 
https://www.butikmasajuzmani.com/

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (37 preceding siblings ...)
  2021-11-16 19:05 ` xecana8007 at funboxcn dot com
@ 2021-11-16 19:08 ` xecana8007 at funboxcn dot com
  2021-11-22  7:37 ` gexed96894 at keagenan dot com
  39 siblings, 0 replies; 41+ messages in thread
From: xecana8007 at funboxcn dot com @ 2021-11-16 19:08 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #38 from tesaso8237 at funboxcn dot comxecana8007@funboxcn.com <xecana8007 at funboxcn dot com> ---
I recently came across your blog and have been reading along. I thought I would
leave my first comment. I don’t know what to say except that I have enjoyed
reading. Nice blog, I will keep visiting this blog very often.
https://www.kedergreenhouse.co.uk/

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
  2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
                   ` (38 preceding siblings ...)
  2021-11-16 19:08 ` xecana8007 at funboxcn dot com
@ 2021-11-22  7:37 ` gexed96894 at keagenan dot com
  39 siblings, 0 replies; 41+ messages in thread
From: gexed96894 at keagenan dot com @ 2021-11-22  7:37 UTC (permalink / raw)
  To: gdb-prs

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

gexed96894 <gexed96894 at keagenan dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gexed96894 at keagenan dot com

--- Comment #39 from gexed96894 <gexed96894 at keagenan dot com> ---
I have been checking out a few of your stories and i can state pretty good
stuff. I will definitely bookmark your blog
buy IPO stocks  https://crosswork.us/

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

end of thread, other threads:[~2021-11-22  7:37 UTC | newest]

Thread overview: 41+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-04 12:57 [Bug backtrace/27147] New: [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) koachan+sourceware at protonmail dot com
2021-01-04 15:58 ` [Bug backtrace/27147] " simark at simark dot ca
2021-01-04 16:26 ` simark at simark dot ca
2021-01-04 18:58 ` simark at simark dot ca
2021-01-04 23:41 ` koachan+sourceware at protonmail dot com
2021-01-04 23:42 ` koachan+sourceware at protonmail dot com
2021-02-18 17:35 ` simark at simark dot ca
2021-02-23 17:48 ` andrew.burgess at embecosm dot com
2021-02-23 18:23 ` andrew.burgess at embecosm dot com
2021-02-23 18:32 ` simark at simark dot ca
2021-02-23 18:33 ` simark at simark dot ca
2021-02-24  9:50 ` andrew.burgess at embecosm dot com
2021-02-24 21:34 ` simark at simark dot ca
2021-02-24 23:39 ` simark at simark dot ca
2021-03-04  0:49 ` simark at simark dot ca
2021-03-04 12:27 ` koachan+sourceware at protonmail dot com
2021-03-04 16:07 ` cvs-commit at gcc dot gnu.org
2021-03-04 17:08 ` cvs-commit at gcc dot gnu.org
2021-03-04 17:09 ` simark at simark dot ca
2021-03-04 17:09 ` simark at simark dot ca
2021-06-27 17:46 ` ahmedsayeed1982 at yahoo dot com
2021-08-10 11:45 ` ucelsanicin at yahoo dot com
2021-08-27 17:52 ` ribevi6798 at enamelme dot com
2021-08-28 18:31 ` buranlevent at yahoo dot com
2021-09-06  9:10 ` focixujo at livinginsurance dot co.uk
2021-09-10 19:40 ` mehmetgelisin at aol dot com
2021-09-14 17:29 ` johnb6174 at gmail dot com
2021-09-14 18:48 ` mark at klomp dot org
2021-09-26 13:31 ` tes.vik1986 at gmail dot com
2021-10-09 11:00 ` gulsenenginar at aol dot com
2021-10-10 16:10 ` oficaj3 at gmail dot com
2021-10-19  7:14 ` progonsaytu at gmail dot com
2021-10-23 13:46 ` fiteva5725 at bomoads dot com
2021-10-24 10:02 ` glassmtech at ukr dot net
2021-10-29 10:57 ` kimolsun2020 at outlook dot com
2021-10-29 12:07 ` huracantili20 at gmail dot com
2021-11-02 15:21 ` gepaw63633 at dukeoo dot com
2021-11-06 21:12 ` paneki8601 at dukeoo dot com
2021-11-16 19:05 ` xecana8007 at funboxcn dot com
2021-11-16 19:08 ` xecana8007 at funboxcn dot com
2021-11-22  7:37 ` gexed96894 at keagenan dot com

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).