diff options
| author | Thomas Schwinge <thomas@codesourcery.com> | 2013-09-25 21:59:24 +0200 |
|---|---|---|
| committer | Thomas Schwinge <thomas@codesourcery.com> | 2013-09-25 21:59:24 +0200 |
| commit | bba1488c7be842e5d0311ffa6541373d63b1164c (patch) | |
| tree | 383f15ec9c57978e5675f0ba03bd94b7cf407731 /open_issues/gdb.mdwn | |
| parent | afce216e724614c6c01ed3ec85f6d5a50dc5037d (diff) | |
| parent | eccdd13dd3c812b8f0b3d046ef9d8738df00562a (diff) | |
Merge remote-tracking branch 'fp/master'
Conflicts:
open_issues/secure_file_descriptor_handling.mdwn
Diffstat (limited to 'open_issues/gdb.mdwn')
| -rw-r--r-- | open_issues/gdb.mdwn | 43 |
1 files changed, 43 insertions, 0 deletions
diff --git a/open_issues/gdb.mdwn b/open_issues/gdb.mdwn index ccc27a14..07b3da45 100644 --- a/open_issues/gdb.mdwn +++ b/open_issues/gdb.mdwn @@ -362,6 +362,18 @@ like `gdb/testsuite/boards/cc-with-tweaks.exp` would help, or setting Cannot access memory at address 0x6c62616e (gdb) testcase ../../../Ferry_Tagscherer/gdb/testsuite/gdb.base/attach-pie-noexec.exp completed in 3 seconds + IRC, freenode, #hurd, 2013-09-06: + + <gnu_srs1> How to debug a program that works in the shell but Cannot + access memory at address ... in gdb? + <tschwinge> Build it without -pie -- but that is just a guess of what + might be going on. + * tschwinge clearly has spent enough time with obscure things to be + able to make such guesses. + <gnu_srs1> tschwinge: looks like -fPIE is used. + <gnu_srs1> verified: some (all?) executables compiled with -fPIE, -fpie + and linked with -pie cannot be debugged in gdb :( + * `solib-event stop` Running ../../../Ferry_Tagscherer/gdb/testsuite/gdb.mi/mi-catch-load.exp ... @@ -547,3 +559,34 @@ like `gdb/testsuite/boards/cc-with-tweaks.exp` would help, or setting related. TODO. + + +# Open Issues + +## [[tag/open_issue_gdb]] + +## `info files` SIGSEGV + +[[!tag open_issue_gdb]] + + +### IRC, freenode, #hurd, 2013-09-07 + + <rekado> I'm trying to debug pfinet, but I'm not very familiar with gdb. + Tried to attach to the running pfinet process (built with debug symbols), + set a breakpoint and ... when I ran "info files" the process segfaulted. + <teythoon> which process segfaults, pfinet or gdb? + <rekado> gdb segfaults. + + +## Watchpoints + +[[!tag open_issue_gdb]] + + +### IRC, freenode, #hurd, 2013-09-16 + + <gnu_srs> tschwinge: Is gdb watch known to fail on hurd? It hangs for me + when logged in via ssh. + <tschwinge> gnu_srs: Don't know about GDB's watch command. Are you sure it + is hanging? |