On Mon, 2008-03-03 at 10:44 +0100, Loïc Minier wrote:
> On Sun, Mar 02, 2008, Sam Morris wrote:
> > > Could you try rebuilding unstable's glib to see whether it
> > > could be a toolchain change?
> >
> > Just tried this; it didn't do any good :(
>
> So the backtraces are borken in 2.14 too i
On Sun, Mar 02, 2008, Sam Morris wrote:
> > Could you try rebuilding unstable's glib to see whether it
> > could be a toolchain change?
>
> Just tried this; it didn't do any good :(
So the backtraces are borken in 2.14 too if you rebuild it?
--
Loïc Minier
On Wed, 2008-02-27 at 10:59 +0100, Loïc Minier wrote:
> On Tue, Feb 26, 2008, Sam Morris wrote:
> > The libglib2.0-0-dbg package in experimental seems not to work. I get
> > loads of backtraces like
>
> This is only with the version in experimental? Or could it be a new
> kernel?
My backtrace
On Tue, Feb 26, 2008, Sam Morris wrote:
> The libglib2.0-0-dbg package in experimental seems not to work. I get
> loads of backtraces like
This is only with the version in experimental? Or could it be a new
kernel? Could you try rebuilding unstable's glib to see whether it
could be a toolchai
Package: libglib2.0-0-dbg
Version: 2.15.6-1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The libglib2.0-0-dbg package in experimental seems not to work. I get
loads of backtraces like:
#0 0xe410 in __kernel_vsyscall ()
#1 0xb70176a7 in poll () from /lib/i686/cmov/libc.
5 matches
Mail list logo