* [Bug c/99649] GDB has issue to show backtrace if the breakpoint is in a function with more then 8 parameters - only for target aarch64-elf ILP32
2021-03-18 15:57 [Bug c/99649] New: GDB has issue to show backtrace if the breakpoint is in a function with more then 8 parameters only in target aarch64-elf ILP32 filip.bascarevic at siemens dot com
@ 2021-03-18 16:04 ` pinskia at gcc dot gnu.org
2021-03-18 16:23 ` filip.bascarevic at siemens dot com
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: pinskia at gcc dot gnu.org @ 2021-03-18 16:04 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99649
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Gdb support for ilp32 has never been committed so I dont see how you are using
it.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug c/99649] GDB has issue to show backtrace if the breakpoint is in a function with more then 8 parameters - only for target aarch64-elf ILP32
2021-03-18 15:57 [Bug c/99649] New: GDB has issue to show backtrace if the breakpoint is in a function with more then 8 parameters only in target aarch64-elf ILP32 filip.bascarevic at siemens dot com
2021-03-18 16:04 ` [Bug c/99649] GDB has issue to show backtrace if the breakpoint is in a function with more then 8 parameters - only for " pinskia at gcc dot gnu.org
@ 2021-03-18 16:23 ` filip.bascarevic at siemens dot com
2021-03-19 7:41 ` [Bug target/99649] " rguenth at gcc dot gnu.org
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: filip.bascarevic at siemens dot com @ 2021-03-18 16:23 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99649
--- Comment #2 from Filip Bascarevic <filip.bascarevic at siemens dot com> ---
Hello Andre,
thank you so much for your quick reply. I also noticed that but somehow with
GCC 8.1 and GDB 8.1 this example works, no GDB endless loop with showing us
backtrace.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug target/99649] GDB has issue to show backtrace if the breakpoint is in a function with more then 8 parameters - only for target aarch64-elf ILP32
2021-03-18 15:57 [Bug c/99649] New: GDB has issue to show backtrace if the breakpoint is in a function with more then 8 parameters only in target aarch64-elf ILP32 filip.bascarevic at siemens dot com
2021-03-18 16:04 ` [Bug c/99649] GDB has issue to show backtrace if the breakpoint is in a function with more then 8 parameters - only for " pinskia at gcc dot gnu.org
2021-03-18 16:23 ` filip.bascarevic at siemens dot com
@ 2021-03-19 7:41 ` rguenth at gcc dot gnu.org
2021-03-22 13:40 ` filip.bascarevic at siemens dot com
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: rguenth at gcc dot gnu.org @ 2021-03-19 7:41 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99649
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|c |target
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
It sounds like this should be a bug for gdb.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug target/99649] GDB has issue to show backtrace if the breakpoint is in a function with more then 8 parameters - only for target aarch64-elf ILP32
2021-03-18 15:57 [Bug c/99649] New: GDB has issue to show backtrace if the breakpoint is in a function with more then 8 parameters only in target aarch64-elf ILP32 filip.bascarevic at siemens dot com
` (2 preceding siblings ...)
2021-03-19 7:41 ` [Bug target/99649] " rguenth at gcc dot gnu.org
@ 2021-03-22 13:40 ` filip.bascarevic at siemens dot com
2021-05-07 7:28 ` stanislav.simek at siemens dot com
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: filip.bascarevic at siemens dot com @ 2021-03-22 13:40 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99649
--- Comment #4 from Filip Bascarevic <filip.bascarevic at siemens dot com> ---
Thank you so much for your replies. I also contacted the GDB community and will
see what will they reply
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug target/99649] GDB has issue to show backtrace if the breakpoint is in a function with more then 8 parameters - only for target aarch64-elf ILP32
2021-03-18 15:57 [Bug c/99649] New: GDB has issue to show backtrace if the breakpoint is in a function with more then 8 parameters only in target aarch64-elf ILP32 filip.bascarevic at siemens dot com
` (3 preceding siblings ...)
2021-03-22 13:40 ` filip.bascarevic at siemens dot com
@ 2021-05-07 7:28 ` stanislav.simek at siemens dot com
2021-05-07 7:43 ` stanislav.simek at siemens dot com
2021-05-14 7:46 ` stanislav.simek at siemens dot com
6 siblings, 0 replies; 8+ messages in thread
From: stanislav.simek at siemens dot com @ 2021-05-07 7:28 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99649
Stanislav Šimek <stanislav.simek at siemens dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |stanislav.simek at siemens dot com
--- Comment #5 from Stanislav Šimek <stanislav.simek at siemens dot com> ---
Hi all,
I would like to add more information for this topic:
This error occurs in case that your function, call the function that has more
than 8 params.
Eq.
int sum(int x1,int x2 int x3,int x4,int x5,int x6,int x7,int x8,int x9 );
int test(int input1 )
{
int c = 0;
if(input1 == 2) // <- If you have breakpoint here, callstack is corrupted
{
c +=input1;
}
c =sum(1,2,3,4,5,6,7,c,input1);
return c;
}
If you remove the call of sum function, then everything works.
If you optimize function " int test(int) " with O0,O1 and O3, it works
Only for O2 this problem occurs.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug target/99649] GDB has issue to show backtrace if the breakpoint is in a function with more then 8 parameters - only for target aarch64-elf ILP32
2021-03-18 15:57 [Bug c/99649] New: GDB has issue to show backtrace if the breakpoint is in a function with more then 8 parameters only in target aarch64-elf ILP32 filip.bascarevic at siemens dot com
` (4 preceding siblings ...)
2021-05-07 7:28 ` stanislav.simek at siemens dot com
@ 2021-05-07 7:43 ` stanislav.simek at siemens dot com
2021-05-14 7:46 ` stanislav.simek at siemens dot com
6 siblings, 0 replies; 8+ messages in thread
From: stanislav.simek at siemens dot com @ 2021-05-07 7:43 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99649
--- Comment #6 from Stanislav Šimek <stanislav.simek at siemens dot com> ---
So isn't it gcc problem?
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug target/99649] GDB has issue to show backtrace if the breakpoint is in a function with more then 8 parameters - only for target aarch64-elf ILP32
2021-03-18 15:57 [Bug c/99649] New: GDB has issue to show backtrace if the breakpoint is in a function with more then 8 parameters only in target aarch64-elf ILP32 filip.bascarevic at siemens dot com
` (5 preceding siblings ...)
2021-05-07 7:43 ` stanislav.simek at siemens dot com
@ 2021-05-14 7:46 ` stanislav.simek at siemens dot com
6 siblings, 0 replies; 8+ messages in thread
From: stanislav.simek at siemens dot com @ 2021-05-14 7:46 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99649
--- Comment #7 from Stanislav Šimek <stanislav.simek at siemens dot com> ---
(In reply to Richard Biener from comment #3)
> It sounds like this should be a bug for gdb.
Hi all,
I would like to add more information for this topic:
This error occurs in case that your function, call the function that has more
than 8 params.
Eq.
int sum(int x1,int x2 int x3,int x4,int x5,int x6,int x7,int x8,int x9 );
int test(int input1 )
{
int c = 0;
if(input1 == 2) // <- If you have breakpoint here, callstack is corrupted
{
c +=input1;
}
c =sum(1,2,3,4,5,6,7,c,input1);
return c;
}
If you remove the call of sum function, then everything works.
If you optimize function " int test(int) " with O0,O1 and O3, it works
Only for O2 this problem occurs.
So isn't it gcc problem?
^ permalink raw reply [flat|nested] 8+ messages in thread