Re: kernel in stable breaks gdb (on merulo)
Hi,
Just to let you know that, while kernel 3.9.8-1 was working fine, the
"gdb stops with SIGTRAP at 0" bug is back with kernel 3.10.5-1 in
today's "Jessie" Testing updates :-(
Émeric
2013/8/8 Ben Hutchings <ben@decadent.org.uk>:
> On Wed, 2013-08-07 at 16:54 -0400, Camm Maguire wrote:
>> Greetings!
>>
>> Stephen Gran <sgran@debian.org> writes:
>>
>> > Hi,
>> >
>> > This one time, at band camp, Patrick Baggett said:
>> > > Hi Camm,
>> > > On Thu, Jul 4, 2013 at 10:51 AM, Camm Maguire <camm@maguirefamily.org>wrote:
>> > >
>> > > > Greetings! gdb stops with SIGTRAP at 0 on merulo, the sole debian ia64
>> > > > porterbox. This is a known bug fixed in later versions of the 3.2
>> > > > kernel series:
>> > > >
>> > > > http://www.mail-archive.com/debian-ia64@lists.debian.org/msg03404.html
>> > > >
>> > > > For some reason we are having trouble upgrading the kernel in the stable
>> > > > release, and debian-admin won't upgrade the merulo kernel without this.
>> > > > What is blocking the progress here?
>> > >
>> >
>> > I would have thought Camm should try, at a guess, the maintainers of
>> > the kernel, as they should have something to do with uploads of the
>> > kernel. Maybe I've missed something, though.
>>
>> Indeed -- thanks! By way of further information, I can report that Dann
>> Frazier has tried the kernel package in stable on his machine and can
>> use gdb without issue. So would it be possible for the kernel
>> maintainers listed above to determine why this bug, ostensibly fixed, is
>> still present at merulo?
>
> Not a clue. Dann is the only kernel maintainer with responsibility for
> ia64 and I'm not sure he has much opportunity to work on it any more.
> I've just fixed occasional build failures; beyond that I don't know or
> care about the platform.
>
> Ben.
>
> --
> Ben Hutchings
> The two most common things in the universe are hydrogen and stupidity.
Reply to: