From: keystroke <zhangrui0000@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Linking error with 8l, guys, could you tell
Date: Thu, 29 Nov 2012 09:48:51 +0000 [thread overview]
Message-ID: <ME8txF.CxB.B.shoe@bath.ac.uk> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
在 2012年11月28日星期三UTC+8下午8时22分30秒,Bence Fábián写道:
> but what is _most_ likely is that you really have them initialized two times.
> just do
> g '(op|et)names ?='
>
> you should find 4 initializations. just delete the redundant ones.
>
>
> 2012/11/28 Bence Fábián <beg...@gmail.com>
>
> DATA opnames<1>+116(SB)/4,$string<1>+739(SB)
>
> and
> DATA etnames<1)+72(SB)/4,$string<1>+912(SB)
>
>
>
>
> are the second initializations of both opnames and etnames.
>
> you can grep for them in the output of
> 8c -S source.c
>
>
> that's all i can help, cause i can't tell what $string<1>+739(SB) and $string<1>+912(SB) refer to
>
>
> since they are adresses.
Thanks guys, I just look into the list, and suprisingly saw you replying in
a new thread, I am not familiar with newsgroup and didn't saw your reply earlier
the problem is solved. It's a good lesson, eyes can lie, I just didn't use machine to check duplicated initializaion.
next reply other threads:[~2012-11-29 9:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 9:48 keystroke [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-29 9:48 keystroke
2012-11-29 9:48 keystroke
2012-11-26 9:49 [9fans] Linking error with 8l, guys, could you tell me where to look? keystroke
2012-11-26 13:25 ` erik quanstrom
2012-11-28 10:20 ` [9fans] Linking error with 8l, guys, could you tell keystroke
2012-11-28 11:43 ` Bence Fábián
2012-11-28 11:51 ` lucio
2012-11-28 12:12 ` Bence Fábián
2012-11-28 12:22 ` Bence Fábián
2012-11-28 12:48 ` erik quanstrom
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=ME8txF.CxB.B.shoe@bath.ac.uk \
--to=zhangrui0000@gmail.com \
--cc=9fans@9fans.net \
/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).