I've the same problem and it gets really impossible to work/debug.
Please fix it as soon as possible. I don't really understand why the
status is still undecided.
--
gdb gets SIGTRAP on every instruction after function call
https://bugs.launchpad.net/bugs/230315
You received this bug notification
according to the bug history this looks like a kernel bug.
** Bug watch added: Debian Bug tracker #475206
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475206
** Also affects: gdb (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475206
Importance: Unknown
Status:
** Changed in: gdb (Debian)
Status: Unknown => New
--
gdb gets SIGTRAP on every instruction after function call
https://bugs.launchpad.net/bugs/230315
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
setting milestone for the linux task; according to the debian log this
is fixed in 2.6.26
** Changed in: linux (Ubuntu Hardy)
Target: None => ubuntu-8.04.1
--
gdb gets SIGTRAP on every instruction after function call
https://bugs.launchpad.net/bugs/230315
You received this bug notificatio
I cannot believe that to change 2 lines of code in the kernel takes half
a year for Ubuntu!
Why are you so neglectful?
--
gdb gets SIGTRAP on every instruction after function call
https://bugs.launchpad.net/bugs/230315
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Changed in: linux (Ubuntu Hardy)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
Status: Confirmed => In Progress
--
gdb gets SIGTRAP on every instruction after function call
https://bugs.launchpad.net/bugs/230315
You received this bug notification because you are a member of Ubun
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
hardy.git;a=commit;h=2ce4b2c2c29f32060580bf37654269a0c15e7845
** Changed in: linux (Ubuntu Hardy)
Status: In Progress => Fix Committed
--
gdb gets SIGTRAP on every instruction after function call
https://bugs.launchpad.net/bugs/230315
You rece
SRU Justification
Impact: gdb is not useable
Patch Description: Fix type in kernel macro
Patch: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
hardy.git;a=commit;h=2ce4b2c2c29f32060580bf37654269a0c15e7845
Test Case: See bug description
--
gdb gets SIGTRAP on every instruction after function ca
Thanks for fixing it.
Now.. would it be possible to inlcude this in hardy-updates soon (not in
a half-year's time)?
--
gdb gets SIGTRAP on every instruction after function call
https://bugs.launchpad.net/bugs/230315
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Thanks for integrating the fix to this bug.
If it would be useful, we can run our test case
against a new patched kernel.
--
gdb gets SIGTRAP on every instruction after function call
https://bugs.launchpad.net/bugs/230315
You received this bug notification because you are a member of Ubuntu
Bugs,
Matthias Klose wrote:
> as a side note, please consider how people may react to your comments. the way
> you raise your voice may not be seen as appropriate by all people.
I considered that thx. I'm just trying to speed up things a bit, because AFAICS
everything is so slow
around bug fixing.
Martin Pitt wrote:
> It might take just 5 minutes to change 2 lines of code, but it takes
> hours of testing the result, testing for regressions, doing QA, and
> processing the update.
I know that. That's why I wrote "soon" instead of "immediately" :)
--
gdb gets SIGTRAP on every instruction af
Same problem here.
Now that it has been found out that this is fixed in 2.6.26, will this be
included in an update _soon_?
Or will there be other solution for this _shortly_?
Imho this should have been fixed already, as others said: "This bug
makes 8.04 completly unusable as a C/C++ development
** Changed in: linux (Ubuntu Hardy)
Target: ubuntu-8.04.1 => ubuntu-8.04.2
--
gdb gets SIGTRAP on every instruction after function call
https://bugs.launchpad.net/bugs/230315
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
Target 8.04.2 -> 2009.01.01? Is this serious?
--
gdb gets SIGTRAP on every instruction after function call
https://bugs.launchpad.net/bugs/230315
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
"This bug makes 8.04 completly unusable as a C/C++ development environment" -->
True
and we have to wait more than 7 months
--
gdb gets SIGTRAP on every instruction after function call
https://bugs.launchpad.net/bugs/230315
You received this bug notification because you are a member of Ubun
We have fixed this bug in Mandriva, patch is here:
http://lkml.org/lkml/2008/7/14/317
** Bug watch added: Mandriva Linux #41361
http://qa.mandriva.com/show_bug.cgi?id=41361
** Also affects: mandriva via
http://qa.mandriva.com/show_bug.cgi?id=41361
Importance: Unknown
Status: Unkn
** Changed in: mandriva
Status: Unknown => Confirmed
--
gdb gets SIGTRAP on every instruction after function call
https://bugs.launchpad.net/bugs/230315
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Now that's good to hear. Now we have to wait 'till the ubuntu
maintainers will release an update. IF they will at all.. :\
--
gdb gets SIGTRAP on every instruction after function call
https://bugs.launchpad.net/bugs/230315
You received this bug notification because you are a member of Ubuntu
Bugs
closing the gdb tasks and the intrepid kernel task
** Changed in: gdb (Ubuntu Hardy)
Status: New => Invalid
** Changed in: gdb (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Hardy)
Importance: Undecided
** Changed in: mandriva
Status: Confirmed => Fix Released
--
gdb gets SIGTRAP on every instruction after function call
https://bugs.launchpad.net/bugs/230315
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Accepted into -proposed, please test and give feedback here. Please see
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
gdb gets SIGTRAP on every instruction after function call
https://
I tried the proposed kernel image, but I still get the SIGTRAP.
uname -a
Linux lab 2.6.24-20-generic #1 SMP Mon Jul 28 13:49:52 UTC 2008 i686 GNU/Linux
I tried the simple testcase mentioned in comment #9. Is it enough to
apt-get install linux-image-2.6.24-20-generic? (by the way I could not
insta
For the record, this only affects i386 arches, so, don't bother to test
it if you are on an amd64 arch.
--
gdb gets SIGTRAP on every instruction after function call
https://bugs.launchpad.net/bugs/230315
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Hi,
I just did an apt-get update, but I still get the 20.38 version:
apt-cache policy linux-image-2.6.24-20-generic
linux-image-2.6.24-20-generic:
Installed: 2.6.24-20.38
Candidate: 2.6.24-20.38
Version table:
*** 2.6.24-20.38 0
400 http://archive.ubuntu.com hardy-proposed/main Pac
linux-image-2.6.24-20-generic in hardy proposed is superseeded by linux-
image-2.6.24-21-generic
--
gdb gets SIGTRAP on every instruction after function call
https://bugs.launchpad.net/bugs/230315
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
What do you mean by superseeded?
apt-cache search cannot find anything greater than -20.
[11:[EMAIL PROTECTED]:~]$ apt-cache search 2.6.24-21
[11:[EMAIL PROTECTED]:~]$
--
gdb gets SIGTRAP on every instruction after function call
https://bugs.launchpad.net/bugs/230315
You received this bug notifi
Hi,
I've just installed:
linux-image-2.6.24-21-generic:
Installed: 2.6.24-21.40
uname -a
Linux lab 2.6.24-21-generic #1 SMP Tue Aug 12 13:37:22 UTC 2008 i686 GNU/Linux
and it works like a charm :)
so.. thank you for applying the patch, and building the new kernel. Now I can
use my machine f
** Tags added: verification-done
** Tags removed: verification-needed
--
gdb gets SIGTRAP on every instruction after function call
https://bugs.launchpad.net/bugs/230315
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
linux 2.6.24-21 copied to hardy-updates.
** Changed in: linux (Ubuntu Hardy)
Status: Fix Committed => Fix Released
--
gdb gets SIGTRAP on every instruction after function call
https://bugs.launchpad.net/bugs/230315
You received this bug notification because you are a member of Ubuntu
Bugs
** Changed in: mandriva
Importance: Unknown => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/230315
Title:
gdb gets SIGTRAP on every instruction after function call
--
ubuntu-bugs mailing
** Changed in: gdb (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/230315
Title:
gdb gets SIGTRAP on every instruction after function call
To manage notifi
** Changed in: gdb (Ubuntu)
Sourcepackagename: None => gdb
--
gdb gets SIGTRAP on every instruction after function call
https://bugs.launchpad.net/bugs/230315
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
This problem appears too when debugging a program with kdevelop:
A message box "Program received signal SIGTRAP (Trace/breakpoint trap)" often
pops up when debugging.
This bug makes 8.04 unusable as a C/C++ development environment
--
gdb gets SIGTRAP on every instruction after function call
http
DEXTER schrieb:
> Thanks for fixing it.
>
> Now.. would it be possible to inlcude this in hardy-updates soon (not in
> a half-year's time)?
setting the milestone doesn't imply a date for the fix, especially that this is
fixed earlier.
as a side note, please consider how people may react to your
DEXTER [2008-08-02 8:34 -]:
> around bug fixing. As I'm using Hardy to develop programs, I know
> how much time it takes to fix 2 lines of code. (should not take
> more than 5 mins)
It might take just 5 minutes to change 2 lines of code, but it takes
hours of testing the result, testing for
DEXTER wrote:
> Target 8.04.2 -> 2009.01.01? Is this serious?
>
Well, you weren't thinking they were going to change kernel version for
8.04, did you?
Guess we'll have to wait for 8.10...
--
gdb gets SIGTRAP on every instruction after function call
https://bugs.launchpad.net/bugs/230315
You r
Hi,
DEXTER [2008-08-11 15:29 -]:
> I tried the proposed kernel image, but I still get the SIGTRAP.
The new version (-20.39) is still building, so you are still using the
old version. Can you please update again in a few hours?
Sorry for the confusion. There is always a few hours of lag betwe
38 matches
Mail list logo