[Bug backtrace/18193] New: corrupted stack frame, symbols only

["admin at typoflash dot com" <sourceware-bugzilla at sourceware dot org>]

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

            Bug ID: 18193
           Summary: corrupted stack frame, symbols only
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: normal
          Priority: P2
         Component: backtrace
          Assignee: unassigned at sourceware dot org
          Reporter: admin at typoflash dot com

Need some help to understand a problem. I debug a c++ program with gdb and
eclipse cdt that uses different syscalls. In rare cases when I set a breakpoint
and look at the call stack, the symbol names are filled with garbage. Only the
symbol names, not the file names and locations. There is no crash and the
program seems to run fine. I can not find an error checking the program with
valgrind and others. But how can gdbs memory space get filled with garbage? A
bad syscall, a bug in gdb or eclipse. What's the best way to find out?

Alex

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