** Changed in: linux-source-2.6.20 (Suse)
Importance: Unknown = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/74691
Title:
Unable to debug under 2.6.22 on i386: Failed to read a valid
Just cleaning up old kernel tasks. I'm going to go ahead and close this
against 2.6.20. Thanks.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Confirmed = Won't Fix
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
from memory
** Changed in: debian
Status: New = Fix Released
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
from memory
https://bugs.launchpad.net/bugs/74691
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Fix Committed = Fix Released
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
from memory
https://bugs.launchpad.net/bugs/74691
You received this bug notification because you are a member of Ubuntu
Bugs,
This should be fixed in gutsy, since 2.6.22-11.32:
[Upstream Kernel Changes]
.
* i386: allow debuggers to access the vsyscall page with compat vDSO
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
from memory
https://bugs.launchpad.net/bugs/74691
You
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: Phillip Lougher = Ben Collins
Status: Confirmed = Fix Committed
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
from memory
https://bugs.launchpad.net/bugs/74691
You received this bug
Dunno if its due to J Kyle's thing but now it seems to be ready for
debugging, can somebody confirm this?
Adding output as seen from gdb, if somebody wants to do some more tests
or something, please lemme know.
** Attachment added: gdb.txt
http://launchpadlibrarian.net/9194453/gdb.txt
--
I haven't made any change, and I'm not getting the failed to read... message.
I think it has been fixed in 2.6.22.11.
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
from memory
https://bugs.launchpad.net/bugs/74691
You received this bug notification because
** Changed in: linux-source-2.6.22 (Ubuntu)
Importance: High = Critical
Assignee: Ben Collins = Phillip Lougher
Target: tribe-6 = ubuntu-7.10-beta
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
from memory
https://bugs.launchpad.net/bugs/74691
I think I may have stumbled on to something interesting playing around
with gdb's settings.
When running inside the gdb command line, but the target program has not
yet run, type `set debug target n' where `n' is any whole integer
greater than or equal to one. Then proceed to run the program
Still happening here, on current Gutsy
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
from memory
https://bugs.launchpad.net/bugs/74691
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
No need for a Gutsy task on the Feisty kernel (in fact should 2.6.20
simply be a WontFix?).
** Changed in: linux-source-2.6.20 (Ubuntu)
Target: tribe-6 = None
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
from memory
** Changed in: debian
Status: Unknown = New
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
from memory
https://bugs.launchpad.net/bugs/74691
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
** Bug watch added: Debian Bug tracker #401482
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401482
** Also affects: debian via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401482
Importance: Unknown
Status: Unknown
--
Unable to debug under 2.6.22 on i386: Failed to read
It seems this bug also affects the Debian kernel packages as well. I
added the appropriate Debian BTS bug number. According to that report,
this problem persists even with Debian's latest 2.6.22 kernels in Sid.
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
** Changed in: linux-source-2.6.20 (Suse)
Status: Confirmed = Invalid
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
from memory
https://bugs.launchpad.net/bugs/74691
You received this bug notification because you are a member of Ubuntu
Bugs, which is
opensuse has fixed the bug with this patch apparently,
https://bugzilla.novell.com/attachment.cgi?id=159330
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
from memory
https://bugs.launchpad.net/bugs/74691
You received this bug notification because you are a
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Fix Released = Confirmed
Target: herd-2 = tribe-6
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Incomplete = Invalid
Target: ubuntu-7.10-beta = tribe-6
--
Unable to debug under 2.6.22 on i386: Failed to read a
It is not invalid at all, it still happens under Gutsy, and there is a
kernel patch for it.
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Invalid = Confirmed
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
from memory
ouch, there was no gdb task ...
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: Matthias Klose = Ben Collins
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
from memory
https://bugs.launchpad.net/bugs/74691
You received this bug notification
i see the same problems in bugzilla.gnome.org, especially for reports from
opensuse and debian 2.18, but fedora 7 also is not really useful currently,
though not that bad as the other ones.
also see https://bugzilla.novell.com/show_bug.cgi?id=258433 , loïc also
commented on that one.
--
** Changed in: linux-source-2.6.22 (Ubuntu)
Target: tribe-5 = ubuntu-7.10-beta
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
from memory
https://bugs.launchpad.net/bugs/74691
You received this bug notification because you are a member of Ubuntu
Bugs,
Definitely still present on 2.6.22-9-generic. Exact same results as
above, x86.
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
from memory
https://bugs.launchpad.net/bugs/74691
You received this bug notification because you are a member of Ubuntu
Bugs, which
Too late for a full kernel upload now, unless this is an unintrusive one
and does not break ABI.
** Changed in: linux-source-2.6.22 (Ubuntu)
Target: tribe-4 = tribe-5
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
from memory
I respectfully submit that on OS which doesn't let developers debug is
not a very useful OS.
If the choice is between breaking ABI (while two months away from 7.10)
and breaking the most basic of functionality for an entire Ubuntu
release, well, I should hope that the choice would be obvious.
If
On Tue, Aug 07, 2007 at 01:47:06PM -, Jon Anderson wrote:
I respectfully submit that on OS which doesn't let developers debug is
not a very useful OS.
If the choice is between breaking ABI (while two months away from 7.10)
and breaking the most basic of functionality for an entire Ubuntu
Ok, so the freeze isn't for Gutsy, but just the next Tribe? That sounds
reasonable.
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
from memory
https://bugs.launchpad.net/bugs/74691
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: linux-source-2.6.20 (Suse)
Status: Unknown = Confirmed
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
from memory
https://bugs.launchpad.net/bugs/74691
You received this bug notification because you are a member of Ubuntu
Bugs, which is
By adding vdso=0 to kernel command line options and rebooting, my
system works well and I can get the following backtrace:
[EMAIL PROTECTED]:~]$ gdb sleep
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
When I execute 'echo 0 /proc/sys/vm/vdso_enabled' with no X server
running and fglrx unloaded, I can no longer input anything via keyboard,
and I can't connect over SSH, either. Not even the power button works.
What's funny is that I *can* switch VTs... other than that, nothing.
--
Unable to
I tried 'echo 0 /proc/sys/vm/vdso_enabled', and my computer locked up
hard. What is a VDSO? Could this lockup be related to FGLRX (it seems
that most lockups are)?
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
from memory
https://bugzilla.novell.com/show_bug.cgi?id=258433 mentions 'echo 0
/proc/sys/vm/vdso_enabled' as a workaround
** Bug watch added: Novell/SUSE Bugzilla #258433
https://bugzilla.novell.com/show_bug.cgi?id=258433
** Also affects: linux-source-2.6.20 (Suse) via
Matthias is investigating if this needs to be fixed in bfd or not.
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) = Matthias Klose
Status: Confirmed = Incomplete
Target: ubuntu-7.10-beta = tribe-4
--
Unable to debug under 2.6.22 on i386: Failed to read a
Ok here's mine :-
[EMAIL PROTECTED]:~$ gdb sleep
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see
For comparison on amd64: with coreutils-dbgsym, I get a good backtrace
and no 'Failed to read a valid object file image from memory.' error.
(gdb) bt
#0 0x2accdc287750 in nanosleep () from /lib/libc.so.6
#1 0x004026b4 in xnanosleep (seconds=value optimized out) at
xnanosleep.c:101
I finally downloaded a i386 desktop CD, and confirm Seb's and Shirish's
finding.
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New = Confirmed
--
Unable to debug under 2.6.22 on i386: Failed to read a valid object file image
from memory
https://bugs.launchpad.net/bugs/74691
You
36 matches
Mail list logo
