* [Fwd: Caught signal 9 in core file ????]
@ 2001-09-27 11:42 Andrew Cagney
2001-09-27 11:49 ` Daniel Jacobowitz
0 siblings, 1 reply; 2+ messages in thread
From: Andrew Cagney @ 2001-09-27 11:42 UTC (permalink / raw)
To: gdb
Anyone want to play with this? While a BFD bug, gdb is probably BFD's
only core file customer.
Andrew
From eliz@is.elta.co.il Thu Sep 27 11:49:00 2001
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: dj@redhat.com
Cc: gcc@gcc.gnu.org, binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: libiberty docs are in
Date: Thu, 27 Sep 2001 11:49:00 -0000
Message-id: <3099-Thu27Sep2001205015+0300-eliz@is.elta.co.il>
References: <200109261856.f8QIuO414025@greed.delorie.com> <1659-Thu27Sep2001121904+0300-eliz@is.elta.co.il> <200109271657.f8RGvLr28862@greed.delorie.com>
X-SW-Source: 2001-09/msg00257.html
Content-length: 1759
> Date: Thu, 27 Sep 2001 12:57:21 -0400
> From: DJ Delorie <dj@redhat.com>
>
> It is only temporary. In case there were bugs, I didn't want to
> burden everyone all at once. When it's proven stable, I'll add it to
> the default rules.
Thank you!
> > I don't recommend using the full @node lines, like this:
> >
> > @node Using,Overview,Top,Top
>
> I couldn't get the auto-node logic to work right in all places. If
> you can, that's good!
I tested "make info" after applying the changes I sent, and it built
without any complaints.
The secret is that you need to lay out the subnodes in the same order
as they are listed in the menus. One of the nodes was out of order,
so I moved it. I'm guessing that this node is what gave you trouble.
> > [Repeat after me: "it's ``occurrence'', not ``occurance'' ;-) May I
> > suggest "M-x ispell-comments-and-strings RET"?]
>
> You may, but I was happy to get what was available in place... :-)
Oops, sorry, I didn't realize you've written the text in the *.c files
as well. I should have looked in the Changelog before releasing silly
jokes.
> > Index: src/libiberty/libiberty.texi
>
> Changelog entry?
Here:
2001-09-27 Eli Zaretskii <eliz@is.elta.co.il>
* libiberty.texi: (Top level): Add syncodeindex pg.
(many nodes): Lose the next,prev,up pointers on the @nide line.
(Using, Supplemental Functions, Replacement Functions): Fix
markup.
(Functions): Move around, to allow makeinfo to build the manual
without next,prev,up pointers in thye node lines.
(Licenses): Fix typos.
* index.c, rindex.c, strchr.c, strerror.c, strrchr.c, strstr.c,
strtol.c, xatexit.c, xexit.c, xmalloc.c: Fix spelling and markup.
* copying-lib.texi: Lose the next,prev,up pointers on the @node
line.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Fwd: Caught signal 9 in core file ????]
2001-09-27 11:42 [Fwd: Caught signal 9 in core file ????] Andrew Cagney
@ 2001-09-27 11:49 ` Daniel Jacobowitz
0 siblings, 0 replies; 2+ messages in thread
From: Daniel Jacobowitz @ 2001-09-27 11:49 UTC (permalink / raw)
To: gdb
On Thu, Sep 27, 2001 at 02:42:26PM -0400, Andrew Cagney wrote:
> Anyone want to play with this? While a BFD bug, gdb is probably BFD's
> only core file customer.
Peter's patch looks right to me, though it's a little more complicated
after my recent BFD core changes - that test will need to be applied in
multiple places, I think.
I'm also not convinced that we can do this reliably; is the thread
which crashed always listed first in a dump? Or should we check that
pr_cursig is not SIGKILL instead?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-09-27 11:49 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-09-27 11:42 [Fwd: Caught signal 9 in core file ????] Andrew Cagney
2001-09-27 11:49 ` Daniel Jacobowitz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox