* Backtrace
@ 2006-09-01 6:48 Matias Sundman (AS/EAB)
2006-09-01 16:42 ` Backtrace Carlos Munoz
0 siblings, 1 reply; 4+ messages in thread
From: Matias Sundman (AS/EAB) @ 2006-09-01 6:48 UTC (permalink / raw)
To: linuxppc-embedded
[-- Attachment #1: Type: text/plain, Size: 558 bytes --]
Comrades,
I would like to do a backtrace in kernel space similar to an oops but then continue the code flow as before i.e. without a crash.
If someone has done anything similar, help and/or tips would be much appreciated!
Cheers //
Matias Sundman
Senior Sw Designer
Ericssonl
IS Ethernet Switch, DIPN
Ericsson AB
Box 1505 Office: +46 8 719 86 83
SE-125 25 ÄLVSJÖ ECN: 850 98683
SWEDEN Mobile: +46 70 267 2405
Visiting address: E-mail: Matias.Sundman@ericsson.com
Armborstvägen 14 Web: http://www.ericsson.com
Älvsjö, STOCKHOLM
[-- Attachment #2: Type: text/html, Size: 2741 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Backtrace
@ 2006-09-01 10:12 KokHow Teh
2006-09-01 10:49 ` Backtrace Matias Sundman (AS/EAB)
0 siblings, 1 reply; 4+ messages in thread
From: KokHow Teh @ 2006-09-01 10:12 UTC (permalink / raw)
To: matias.sundman; +Cc: linuxppc-embedded
Hi;
Is using hardware/software breakpoint with a hardware debugger wh=
at
you are looking for?
Regards,
Teh
"Matias Sundman \(AS/EAB\)" <matias.sundman@ericsson.com>@ozlabs.org on=
09/01/2006 02:48:43 PM
Sent by: linuxppc-embedded-bounces+kokhow.teh=3Dmarconi.com@ozlabs.o=
rg
To: <linuxppc-embedded@ozlabs.org>
cc:
Subject: Backtrace
Comrades,
I would like to do a backtrace in kernel space similar to an oops but t=
hen
continue the code flow as before i.e. without a crash.
If someone has done anything similar, help and/or tips would be much
appreciated!
Cheers //
Matias Sundman
Senior Sw Designer
Ericssonl
IS Ethernet Switch, DIPN
Ericsson AB
Box 1505=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0=
Office: +46=A0 8 719 86 83
SE-125 25 =C4LVSJ=D6=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 ECN:=A0=
=A0=A0 850 98683
SWEDEN=A0 =A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 Mobile: +46 70 26=
7 2405
Visiting address:=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0E-mail: Matias=
.Sundman@ericsson.com
Armborstv=E4gen 14=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 Web:=A0=A0=
=A0 http://www.ericsson.com
=C4lvsj=F6, STOCKHOLM
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
=
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: Backtrace
2006-09-01 10:12 Backtrace KokHow Teh
@ 2006-09-01 10:49 ` Matias Sundman (AS/EAB)
0 siblings, 0 replies; 4+ messages in thread
From: Matias Sundman (AS/EAB) @ 2006-09-01 10:49 UTC (permalink / raw)
To: linuxppc-embedded; +Cc: Örjan Gustavsson (AS/EAB)
=20
Hello,
We have HW debuggers ; Windriver ICE and BDI2000 , but in our specific =
scenario the system is up=20
and running and we cannot be breakpoint intrusive, other parts of the =
system would be affected ( and our own blade ).
No, what we would like to do is that when a specific condition is met a =
backtrace printout
is performed and after that the system runs as designed.
:
[Existing code]
:=20
:
if ( some_variable =3D=3D my_condition )
{
print_out_backtrace();
}
:
:
[Existing code]
:=20
:
We have implemented "forced" kernel ooops:es in "print_out_backtrace();" =
but we would like to=20
have controlled backtraces ;-))
This is in Kernel space on a ppc8270.=20
Cheers // Matias
-----Original Message-----
From: KokHow Teh [mailto:KokHow.Teh@marconi.com]=20
Sent: den 1 september 2006 12:13
To: Matias Sundman (AS/EAB)
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Backtrace
Hi;
Is using hardware/software breakpoint with a hardware debugger =
what
you are looking for?
Regards,
Teh
"Matias Sundman \(AS/EAB\)" <matias.sundman@ericsson.com>@ozlabs.org on
09/01/2006 02:48:43 PM
Sent by: =
linuxppc-embedded-bounces+kokhow.teh=3Dmarconi.com@ozlabs.org
To: <linuxppc-embedded@ozlabs.org>
cc:
Subject: Backtrace
Comrades,
I would like to do a backtrace in kernel space similar to an oops but =
then
continue the code flow as before i.e. without a crash.
If someone has done anything similar, help and/or tips would be much
appreciated!
Cheers //
Matias Sundman
Senior Sw Designer
Ericssonl
IS Ethernet Switch, DIPN
Ericsson AB
Box 1505=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 =
=A0=A0=A0=A0=A0=A0=A0 Office: +46=A0 8 719 86 83
SE-125 25 =C4LVSJ=D6=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 =
ECN:=A0=A0=A0 850 98683
SWEDEN=A0 =A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 Mobile: +46 70 267 =
2405
Visiting address:=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0E-mail: =
Matias.Sundman@ericsson.com
Armborstv=E4gen 14=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 =
Web:=A0=A0=A0 http://www.ericsson.com
=C4lvsj=F6, STOCKHOLM
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Backtrace
2006-09-01 6:48 Backtrace Matias Sundman (AS/EAB)
@ 2006-09-01 16:42 ` Carlos Munoz
0 siblings, 0 replies; 4+ messages in thread
From: Carlos Munoz @ 2006-09-01 16:42 UTC (permalink / raw)
To: Matias Sundman (AS/EAB); +Cc: linuxppc-embedded
Matias Sundman (AS/EAB) wrote:
> Comrades,
> I would like to do a backtrace in kernel space similar to an oops but
> then continue the code flow as before i.e. without a crash.
>
Try dump_stack(). It should do what you want.
Carlos
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2006-09-01 17:03 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-09-01 6:48 Backtrace Matias Sundman (AS/EAB)
2006-09-01 16:42 ` Backtrace Carlos Munoz
-- strict thread matches above, loose matches on Subject: below --
2006-09-01 10:12 Backtrace KokHow Teh
2006-09-01 10:49 ` Backtrace Matias Sundman (AS/EAB)
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.