From: Andrew Lunn <andrew@lunn.ch>
To: harmon <lharmon@neo.rr.com>
Cc: 'Andrew Lunn' <andrew@lunn.ch>, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] need debugging help
Date: Thu, 05 Aug 2004 16:24:00 -0000 [thread overview]
Message-ID: <20040805162149.GA27052@lunn.ch> (raw)
In-Reply-To: <000401c47b00$fe330730$8601a8c0@k7sem>
On Thu, Aug 05, 2004 at 11:29:23AM -0400, harmon wrote:
> Thanks for the advice. I figured out how to enable asserts, enabled
> them, ran my application and asserted where I was having a problem:
>
> The message is:
> ASSERT FAIL: <6>mutex.cxx[249]cyg_bool Cyg_Mutex::lock() Locking mutex I
> already own
> ASSERT FAIL: <6>mutex.cxx [249] cyg_bool Cyg_Mutex::lock()
>
>
> This problem occurs where I call
> cyg_flag_setbits(&UsbRspStateFlag,
> (1<<USB_STATE_IN_MESSAGE_DONE));
> from a DSR.
>
> I believe this might be a point where my DSR calls cyg_flag_setbits
> twice, once for each thread, and the second call results in problems.
No, that does not sound right. cyg_flash_setbits should not be doing
anything with mutex's. Also, you should not be using mutex's inside a
DSR. I think the mutex problem is being triggered from some other
location. You should be able to put a breakpoint in cyg_assert_failed
and then get a backtrace from gdb.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2004-08-05 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 17:42 harmon
2004-08-04 18:59 ` Andrew Lunn
2004-08-05 15:29 ` harmon
2004-08-05 16:24 ` Andrew Lunn [this message]
2004-08-05 17:20 ` harmon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040805162149.GA27052@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@sources.redhat.com \
--cc=lharmon@neo.rr.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).