lkml.org 
[lkml]   [2004]   [Jan]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: PPC KGDB changes and some help?
Tom Rini wrote:
>
>>There is a real danger of passing signal info back to gdb as it will want
>>to try to deliver the signal which is a non-compute in most kgdbs in the
>>field. I did put code in the mm-kgdb to do just this, but usually the
>>arrival of such a signal (other than SIGTRAP) is the end of the kernel.
>>All that is left is to read the tea leaves.
>
>
> The gdb I've been testing this with knows better than to try and send a
> singal back, so that's not a worry. The motivation behind doing this
> however is along the lines of "if it ain't broke, don't remove it". The
> original stub was getting all of this information correctly, so why stop
> doing it?
>
You sure. If so what gdb? And how does it know? I suppose you could tell it
with a script, but then what if one forgets?

--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:00    [W:0.205 / U:1.888 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site