From: Elena Zannoni <ezannoni@redhat.com>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: ezannoni@redhat.com, fedor@doc.com, cagney@gnu.org,
gdb-patches@sources.redhat.com
Subject: Re: [rfa/symtab] Move find_pc_section call to lookup_minimal_symbol_by_pc
Date: Mon, 16 Feb 2004 18:11:00 -0000 [thread overview]
Message-ID: <16433.1743.781290.240346@localhost.redhat.com> (raw)
In-Reply-To: <20040209215812.6112F4B363@berman.michael-chastain.com>
Michael Elizabeth Chastain writes:
> The filenames are a problem because gdb1237-1280-main.c
> and gdb1237-1280.c are not 8.3 unique.
>
> You either have to make them 8.3 unique (preferred) or
> add lines to config/djgpp/fnchange.lst.
>
I created a new PR to include both problems and use that new number. PR/1555.
> For the kfail's, please use more specific patterns than just
> ".*$gdb_prompt $". kfail's should be for known bugs, which means
> there should be known-bad output. If the output doesn't match a
> specific known-bad output, then it means that gdb has regressed
> even more, and the KFAIL turns into a FAIL (this does happen).
>
I am not sure what to do here, except start adding patterns.
> You don't need to call get_compiler_info unless you use one of
> these functions or data symbols later: test_compiler_info,
> gcc_compiled, hp_cc_compiler, hp_aCC_compiler, signed_keyword_not_used.
>
it is using gcc_compiled to figure out the flags to build the shlibs.
> I missed the beginning of the thread, but it helps to say what
> system(s) you tested it on (so when it breaks on a different system
> later, it makes it easier to figure out what is wrong ... morbid
> but true).
>
Adam?
I'd like to close this thread and get the test in.
elena
next prev parent reply other threads:[~2004-02-16 18:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 21:58 Michael Elizabeth Chastain
2004-02-10 16:38 ` Adam Fedor
2004-02-16 18:11 ` Elena Zannoni [this message]
2004-02-17 4:47 ` Adam Fedor
2004-02-17 5:00 ` Daniel Jacobowitz
2004-02-17 14:23 ` Elena Zannoni
2004-02-18 3:40 ` Adam Fedor
-- strict thread matches above, loose matches on Subject: below --
2004-01-27 22:23 Andrew Cagney
2004-01-27 22:52 ` Daniel Jacobowitz
2004-01-29 20:15 ` Elena Zannoni
2004-01-29 23:22 ` Andrew Cagney
2004-01-30 3:30 ` Adam Fedor
2004-01-30 4:53 ` Adam Fedor
2004-02-04 22:25 ` Elena Zannoni
2004-02-09 4:26 ` Adam Fedor
2004-02-09 15:31 ` Elena Zannoni
2004-01-30 3:29 ` Adam Fedor
2004-02-04 22:20 ` Elena Zannoni
2004-02-04 23:06 ` Andrew Cagney
2004-02-06 18:59 ` Andrew Cagney
2004-02-08 5:17 ` Adam Fedor
2004-02-09 15:35 ` Elena Zannoni
2004-02-09 16:40 ` Andrew Cagney
2004-02-09 17:54 ` Joel Brobecker
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=16433.1743.781290.240346@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=cagney@gnu.org \
--cc=fedor@doc.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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