From: Daniel Berlin <dan@cgsoftware.com>
To: jtc@redback.com
Cc: RDBrown@mira.net, RodneyBrown@mynd.com, gdb-patches@sources.redhat.com
Subject: Re: PATCH: gdb/corefile.c (0401 snap on HP-UX).
Date: Tue, 10 Apr 2001 16:14:00 -0000 [thread overview]
Message-ID: <m2snjg4abv.fsf@dynamic-addr-83-177.resnet.rochester.edu> (raw)
In-Reply-To: <5mhezy6l5z.fsf@jtc.redback.com>
jtc@redback.com (J.T. Conklin) writes:
> >>>>> "RDBrown" == RDBrown <RDBrown@mira.net> writes:
> RDBrown> gdb/corefile.c was failing to compile with a missing
> RDBrown> declaration for `symfile_objfile'. This allows gdb to build,
> RDBrown> but still hangs when starting the child process.
>
> Our discussions about removing unnecessary header files and a include
> file coventions didn't cover situations like this. While I expected
> some fallout from removing "unnecessary" headers, I thought they would
> occur because macroes defined in a target's tm-*.h or nm-*.h headers
> would require declarations from one of GDB's headers (like regcache.h,
> etc.). This is a bit different, because host specific behavior is in
> a common source file.
>
>
> I'm not sure that I like this patch, but I'm not sure I can come up
> with a resonable alternative in the short term. Perhaps the code to
> find the symbol file cooresponding to the core file (this is the bit
> that needs symfile_objfile) should be replaced with a config specific
> hook. But because it is also wrapped with HPUXHPPA, I'm not opposed
> to checking this in now, and fixing it up later.
Please don't.
The idea is not to *add* things wrapped with HPUXHPPA, rather, remove them.
Pretending they will be fixed up later isn't a good idea. They haven't
been thus far. There is no indication this will change.
If you must add those headers, add them unconditionally. Let's not add
another HPUXHPPA ifdef.
>
> Would anyone else care to share their thoughts? If there are no
> objections, I'll get this patch committed soon.
>
> --jtc
>
> --
> J.T. Conklin
> RedBack Networks
--
I bought a dog the other day... I named him Stay. It's fun to
call him... "Come here, Stay! Come here, Stay!" He went
insane. Now he just ignores me and keeps typing. He's an East
German Shepherd.
next prev parent reply other threads:[~2001-04-10 16:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-09 6:03 RDBrown
2001-04-09 10:17 ` Kevin Buettner
2001-04-10 17:46 ` J.T. Conklin
2001-04-12 9:40 ` J.T. Conklin
2001-04-09 10:24 ` J.T. Conklin
2001-04-10 16:14 ` Daniel Berlin [this message]
2001-04-10 17:51 ` J.T. Conklin
2001-04-10 21:06 ` Daniel Berlin
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=m2snjg4abv.fsf@dynamic-addr-83-177.resnet.rochester.edu \
--to=dan@cgsoftware.com \
--cc=RDBrown@mira.net \
--cc=RodneyBrown@mynd.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jtc@redback.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