9-25 11:41:20.0 +
+++ valgrind-3.11.0/debian/changelog 2016-06-19 00:01:35.0 +
@@ -1,3 +1,10 @@
+valgrind (1:3.11.0-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Add 15_compressed.patch - support compressed debug info (closes: #810295)
+
+ -- Max Dmitrichenko S
Package: fglrx-source
Version: 1:12-1-1~bpo60+1
Severity: serious
Justification: fails to build from source
I had binutils-gold packages installed and this was the reason that kernel
module failed to build on my machine.
-- Package-specific info:
VGA-compatible devices on PCI bus:
01:00.0 VGA co
Ok. Seems that bug is fixed in experimental. Two questions.
1) Will this version be uploaded to unstable and then to testing
before lenny is released?
2) According to Ben, any library on SPARC is a subject to this bug. I
think it is rather hard to create a list of libraries which have
functions w
>> * When a newer compiler package is available for a distribution, is
>> everything rebuilt with it?
>>
>No.
But this is definitely non-sense. IIRC potentially every library is a
subject to be affected by the compiler's bug. The fact that other libs
don't cause such a destructive behavior (as
2008/11/6, Julien Cristau <[EMAIL PROTECTED]>:
> Actually, it works just fine here, so that justification seems wrong.
> You didn't send your config or log, though, so it's hard to tell.
Indeed. It works. This behavior seems to be linked with similar evdev
bug because now with new evdev driver syn
Package: xserver-xorg-input-synaptics
Version: 0.14.7~git20070706-4~dmitrmax.1
Severity: grave
Tags: patch
Justification: renders package unusable
Driver forgets to ungrab the event device so the next time it is grabbed EBUSY
is returned.
This happens e.g. when I logoff from KDE session and retu
Synaptics driver on my laptop also has the same bug. In this light, I
suspect that X server input layer introduces some change which breaks
input drivers.
Can someone with more detailed knowledge of X investigate this problem?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "un
2008/11/5, Modestas Vainius <[EMAIL PROTECTED]>:
> Hello,
>
> antradienis 04 Lapkritis 2008, Max Dmitrichenko rašė:
>> addresses. GDB's backtrace is attached.
> Is it? I don't see an attachment.
Oops... Another try :)
>> What's next? Is there a way to
Thanks Modestas!
Running kicker --nofork under gdb produces the same crash with SIGBUS.
Tested several times - backtrace doesn't differ except for object
addresses. GDB's backtrace is attached.
What's next? Is there a way to build only kicker from sources? Not
necessary to build a package. Rebuil
Proposed patch. Explanations here [1].
[1] http://marc.info/?l=linux-kernel&m=122545873605649&w=2
--
Max
diff -uprN linux-source-2.6.26/arch/sparc64/kernel/pci.c linux-source-2.6.26.pci-fixed/arch/sparc64/kernel/pci.c
--- linux-source-2.6.26/arch/sparc64/kernel/pci.c 2008-07-14 01:51:29.000
2008/10/29, Gaudenz Steinlin <[EMAIL PROTECTED]>:
> Hi Max
>
> Thanks for testing. IMO the situation is now much more clear. I'm happy
> that you confirmed that the patched kernel fixes the problem with the
> X server in lenny.
Read carefully, Gaudenz. Patched kernel fixes only driver misbehaviour
Package: xserver-xorg-core
Version: 2:1.5.2-1
Followup-For: Bug #500358
I've installed the xserver-xorg 1.5 and mach64 driver from experimental
and tested it with:
1) Current lenny's kernel
2) Gaudenz's patched kernel
3) etchnhalf kernel (2.6.24)
All the tests have the same negative result. Lo
Package: xserver-xorg-core
Version: 2:1.4.2-7
Followup-For: Bug #500358
Indeed, the Gaudenz's kernel helps to get rid of "INVALID MEM ALLOCATION"
messages in the log. But the final result is that last lines of log change
from:
(WW) MACH64: Mach64 in slot 1:2:0 could not be detected!
(II) UnloadMo
Package: eciadsl
Version: 0.11-3.1
Severity: grave
Justification: renders package unusable
Switching to kernel version 2.6.18 has made the eciadsl completly unusable for
the owners of GlobSpan-based modems. But there is a patch published on the
homepage of the package which restores the normal fun
Package: eclipse-gcj
Version: 3.2.1-4
Severity: grave
Justification: renders package unusable
I'm trying to install Eclipse on sparc architecture. That's what I get:
# LANG=en_US.UTF-8 apt-get install eclipse-gcj
Reading package lists... Done
Building dependency tree... Done
Some packages could no
15 matches
Mail list logo
