Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #58529 > unrolled thread
| Started by | "Sigmund Scholz" <s.scholz859@gmx.de> |
|---|---|
| First post | 2017-07-27 08:10 +0200 |
| Last post | 2017-09-25 03:40 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.kernel
Bug#869853: Known issues with gdb in rt-20-patch "Sigmund Scholz" <s.scholz859@gmx.de> - 2017-07-27 08:10 +0200
Bug#869853: marked as done (Known issues with gdb in rt-20-patch) owner@bugs.debian.org (Debian Bug Tracking System) - 2017-09-25 03:40 +0200
| From | "Sigmund Scholz" <s.scholz859@gmx.de> |
|---|---|
| Date | 2017-07-27 08:10 +0200 |
| Subject | Bug#869853: Known issues with gdb in rt-20-patch |
| Message-ID | <u7K9H-2u0-1@gated-at.bofh.it> |
Package: linux-image-4.9.0-3-rt-amd64
Version: 4.9.30-2+deb9u2
With the current and all previous rt-kernel package for debian 9 it is almost impossible to use gdb for debugging.
Kernel.release:
4.9.30-rt20
Known issues in rt-20-patch :
gdb. While gdb is following a task it is possible that after a
fork() operation the task is waiting for gdb and gdb waiting
for the task.
In rt-21-patch the problem is solved!
My wish:
using rt-21-patch or newer in next update
Thanks for attention
[toc] | [next] | [standalone]
| From | owner@bugs.debian.org (Debian Bug Tracking System) |
|---|---|
| Date | 2017-09-25 03:40 +0200 |
| Subject | Bug#869853: marked as done (Known issues with gdb in rt-20-patch) |
| Message-ID | <utqxj-7O2-3@gated-at.bofh.it> |
| In reply to | #58529 |
[Multipart message — attachments visible in raw view] — view raw
Your message dated Mon, 25 Sep 2017 02:27:28 +0100 with message-id <1506302848.2852.62.camel@decadent.org.uk> and subject line Re: Bug#869853: Known issues with gdb in rt-20-patch has caused the Debian Bug report #869853, regarding Known issues with gdb in rt-20-patch to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 869853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869853 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web