From: Andrew Cagney <ac131313@cygnus.com>
To: Fernando Nasser <fnasser@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfc] Add uiout param to libgdb functions
Date: Sat, 08 Sep 2001 10:33:00 -0000 [thread overview]
Message-ID: <3B9A565D.8050601@cygnus.com> (raw)
In-Reply-To: <3B9A5127.9DA9D30F@redhat.com>
> Andrew Cagney wrote:
>
>>
>> Hello,
>>
>> The attached adds a UIOUT param to the libgdb function calls. Any
>> thoughts, it is really pretty straight forward.
>>
>
>
> Sure thing.
>
> If I remember well we could not do it before because of the non-uiout
> code
> that was still around.
not sure, i think it was more that uiout wasn't being passed around.
catch_exceptions() covers this problem by installing the explicit uiout
parameter for the lifetime of the call. c.f. gdb internals doco.
next is a stop reason query. keith, you can start thinking about buying
some champagne :-)
andrew
next prev parent reply other threads:[~2001-09-08 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-08 9:48 Andrew Cagney
2001-09-08 10:14 ` Fernando Nasser
2001-09-08 10:33 ` Andrew Cagney [this message]
2001-09-17 21:24 ` Andrew Cagney
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=3B9A565D.8050601@cygnus.com \
--to=ac131313@cygnus.com \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.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