unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Han-Wen Nienhuys  <hanwen@xs4all.nl>
Cc: jantien@xs4all.nl, guile-devel@gnu.org
Subject: Re: stumped by scm_car/scm_cdr
Date: Sun, 26 Sep 2004 01:19:21 +0200	[thread overview]
Message-ID: <16725.64761.208412.328474@byrd.xs4all.nl> (raw)
In-Reply-To: <87zn3e739g.fsf@zagadka.ping.de>

mvo@zagadka.de writes:
> Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
> 
> > I have a problem that I cannot make heads of tails from.
> > [...]
> > What could be going on here?
> 
> Tough.  In case you didn't try this already, I would recompile Guile
> and LilyPond without optimization (CFLAGS="-g").  That should give
> better GDB output.  Hopefully the bug wont disappear by that...
> 
> Do you use threads in the example?

No.

> From what context is
> _lll_mutex_lock_wait being called?

I tried setting a breakpoint on this function, but if I do, the run
completes as expected normally.

-- 

 Han-Wen Nienhuys   |   hanwen@xs4all.nl   |   http://www.xs4all.nl/~hanwen 



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2004-09-25 23:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-24 23:29 stumped by scm_car/scm_cdr Han-Wen Nienhuys
2004-09-25 15:54 ` Marius Vollmer
2004-09-25 23:19   ` Han-Wen Nienhuys [this message]
2004-09-29 15:37     ` Marius Vollmer
2004-10-06 23:44       ` Han-Wen Nienhuys
2004-10-07 18:52         ` Han-Wen Nienhuys
2004-10-07 21:55           ` Marius Vollmer
2004-10-07 22:12         ` Marius Vollmer
2004-10-07 22:51           ` Han-Wen Nienhuys
2004-10-07 23:41             ` Han-Wen Nienhuys
2004-10-18 17:47             ` Marius Vollmer
2004-10-24 12:25               ` Han-Wen Nienhuys
2004-11-04 16:49                 ` Marius Vollmer
2004-11-08  6:48           ` Dirk Herrmann

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16725.64761.208412.328474@byrd.xs4all.nl \
    --to=hanwen@xs4all.nl \
    --cc=guile-devel@gnu.org \
    --cc=jantien@xs4all.nl \
    /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).