From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Cc: Paul Brook <paul@codesourcery.com>
Subject: Re: [PATCH] Ping - PR1473
Date: Mon, 05 Jan 2004 21:06:00 -0000 [thread overview]
Message-ID: <20040105210626.GA11599@nevyn.them.org> (raw)
In-Reply-To: <200401051128.37903.paul@codesourcery.com>
On Mon, Jan 05, 2004 at 11:28:37AM +0000, Paul Brook wrote:
> I submitted a patch to fix PR1473 a couple of weeks ago, but haven't recieved
> any feedback.
>
> http://sources.redhat.com/ml/gdb-patches/2003-12/msg00426.html
>
> I forgot to put [patch] in the subject line, so I guess it might have slipped
> past unnoticed.
It slipped past because no one likes to deal with infrun :)
I don't like the idea of adding this test to keep_going. This should
only be necessary in the BPSTAT_WHAT_CHECK_SHLIBS case, correct?
Somethng like this:
- if (stop_on_solib_events)
+ if (stop_on_solib_events || stop_stack_dummy)
I don't know if you need a stop_print_frame=0 also if
(stop_stack_dummy).
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-05 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 11:28 Paul Brook
2004-01-05 21:06 ` Daniel Jacobowitz [this message]
2004-01-21 16:12 ` Paul Brook
2004-01-21 16:18 ` Daniel Jacobowitz
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=20040105210626.GA11599@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=paul@codesourcery.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