On 4/6/11 10:17 AM, Julian Elischer wrote:
On 4/6/11 5:45 AM, John Baldwin wrote:
On Tuesday, April 05, 2011 4:35:44 pm Navdeep Parhar wrote:
On Tue, Apr 5, 2011 at 1:33 PM, Julian
Elischer wrote:
On 4/4/11 6:04 PM, Justin Hibbits wrote:
What does ddb do? It always seems to get this stuff
On 4/6/11 5:45 AM, John Baldwin wrote:
On Tuesday, April 05, 2011 4:35:44 pm Navdeep Parhar wrote:
On Tue, Apr 5, 2011 at 1:33 PM, Julian Elischer wrote:
On 4/4/11 6:04 PM, Justin Hibbits wrote:
What does ddb do? It always seems to get this stuff correct.
ddb knows to stop when it gets to
On Tuesday, April 05, 2011 4:35:44 pm Navdeep Parhar wrote:
> On Tue, Apr 5, 2011 at 1:33 PM, Julian Elischer wrote:
> > On 4/4/11 6:04 PM, Justin Hibbits wrote:
> >>
> >> On Apr 4, 2011, at 6:57 PM, Julian Elischer wrote:
> >>>
> >>> is there anyone here with enough gdb/kgdb source experience to
On Monday, April 04, 2011 9:04:23 pm Justin Hibbits wrote:
> On Apr 4, 2011, at 6:57 PM, Julian Elischer wrote:
> > is there anyone here with enough gdb/kgdb source experience to know
> > what
> > we would need to put on the stack at fork_exit() to make it stop
> > when it
> > gets there?
> >
>
On 4/5/11 1:35 PM, Navdeep Parhar wrote:
On Tue, Apr 5, 2011 at 1:33 PM, Julian Elischer wrote:
On 4/4/11 6:04 PM, Justin Hibbits wrote:
On Apr 4, 2011, at 6:57 PM, Julian Elischer wrote:
is there anyone here with enough gdb/kgdb source experience to know what
we would need to put on the stac
On Tue, Apr 5, 2011 at 1:33 PM, Julian Elischer wrote:
> On 4/4/11 6:04 PM, Justin Hibbits wrote:
>>
>> On Apr 4, 2011, at 6:57 PM, Julian Elischer wrote:
>>>
>>> is there anyone here with enough gdb/kgdb source experience to know what
>>> we would need to put on the stack at fork_exit() to make i
On 4/4/11 6:04 PM, Justin Hibbits wrote:
On Apr 4, 2011, at 6:57 PM, Julian Elischer wrote:
is there anyone here with enough gdb/kgdb source experience to know
what
we would need to put on the stack at fork_exit() to make it stop
when it
gets there?
not only is it annoying but it slows down d
On Apr 4, 2011, at 6:57 PM, Julian Elischer wrote:
is there anyone here with enough gdb/kgdb source experience to know
what
we would need to put on the stack at fork_exit() to make it stop
when it
gets there?
not only is it annoying but it slows down debugging because kgdb and
the ddd
fron
currently in kernel stack traces I see:
[Switching to Thread 100246]
0x814617f3 in fio_local_to_global_packet () from
x/mumble.ko
(kgdb) bt
#0 0x814617f3 in () from x/mumble.ko
#1 0x8146171f in () from x/mumble.ko
[...]
#14 0x8
