Re: Exact Place at which my application goes weird

On Feb 6, 8:07 pm, "Boudewijn Dijkstra" <boudew...@xxxxxxxxx> wrote:
Op Tue, 06 Feb 2007 14:42:27 +0100 schreef karthikbg
<karthik.balag...@xxxxxxxxxxxxxxx>:

My application goes into a Deadlock condition OR some_Unknown_Problem.
If i use JTAG and do 'Connect' , can i get the exact place of problem

It's possible.

OR atleast near to the place of problem ?

That's less unlikely.

Any other ideas ??

* use your high-level debugger
* design for testability
* don't design a system that can deadlock
* eliminate the possibility or likelihood of some_Unknown_Problem

I Use CCS(Code Composer Studio) & OMAP.

--
Gemaakt met Opera's revolutionaire e-mailprogramma: http://www.opera.com/mail/


Fine. Thx for your ideas.

My VxWorks application goes into Deadlock condition.
How to View/Identify Reason for Deadlock using VxWorks ? I would
like
to know a built-in feature in Vxworks that will help in identifying
the Deadlock condition and tell me the reasons for the Deadlock .

I do not want to use this programming approach for finding the reason
for Deadlock.

Is there any Feature in Vxworks for identifying the deadlock reason ?
I do not find any info for Finding the Reason for Deadlock using
VxWorks.
I use PowerPC. Kindly provide me some solution for this .

Thx in advans,
Karthik Balaguru




.

Relevant Pages

  • Re: Exact Place at which my application goes weird
    ... How do you know it is a deadlock and not an infinite loop or other ... to know a built-in feature in Vxworks that will help in identifying ... I do not want to use this programming approach for finding the reason ...
    (comp.arch.embedded)
  • Re: [ofa-general] Re: Demand paging for memory regions
    ... you could do this without a new chip design in general. ... Lot's of RDMA ... host memory so they are already designed to hang onto packets during ... pages and then putting the storage over IB would be deadlock ...
    (Linux-Kernel)
  • Re: Prevents Events From Interrupting Events
    ... download. ... Since your design already has a deadlock condition as it is, I would be surprised if you can fix that basic design issue by adding a new thread and you could easily just make it harder to fix. ... you can use the lockstatement or similar synchronization mechanism multiple times without any trouble. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: How to programmatically avoid deadlock?
    ... schemes don't seem to realize this. ... directly in a programming language. ... a deadlock isn't a bug. ... or even a wrong design. ...
    (comp.programming.threads)
  • Re: Disabling automatic kill of a deadlocked process
    ... > The reason I am asking is that for some reason the automatic kill is never ... Are you 100% certain is really was a *deadlock* and not just ordinary blocking? ... > occuring on the customer site and their dba doesn't know how this was ...
    (microsoft.public.sqlserver.server)