From: "Micah Stetson" <micah@stetsonnet.org>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] setmalloctag in cc.a?
Date: Sun, 31 Dec 2006 17:29:38 -0800 [thread overview]
Message-ID: <b3b4f6f30612311729x4d73f1c2ofd39b531e0a58983@mail.gmail.com> (raw)
In-Reply-To: <63b300555de7d71e2c7ec23233591d6b@terzarima.net>
> >/sys/src/cmd/cc does this, but I don't understand why. I don't see
> >any place where setmalloctag is called, so why is 8l trying to pull it
> >in?
>
> something else in libc calls it, and it can't load both malloc definitions.
Hum. I looked for that and didn't see it... I'll check again.
Micah
next prev parent reply other threads:[~2007-01-01 1:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-31 17:53 Micah Stetson
2006-12-31 19:51 ` Charles Forsyth
2007-01-01 1:29 ` Micah Stetson [this message]
2007-01-01 6:19 ` Micah Stetson
2007-01-01 10:18 ` Charles Forsyth
[not found] ` <66f4993796d468c324e7cd31e6c8c74e@proxima.alt.za>
2007-01-02 5:39 ` Micah Stetson
2007-01-03 4:06 ` lucio
2007-01-03 16:44 ` Micah Stetson
2007-02-06 4:46 ` Lucio De Re
2007-02-06 5:41 ` Lucio De Re
2007-02-06 6:31 ` Bruce Ellis
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=b3b4f6f30612311729x4d73f1c2ofd39b531e0a58983@mail.gmail.com \
--to=micah@stetsonnet.org \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).