From: "Edward Peschko" <horos11@gmail.com>
To: "Michael Snyder" <msnyder@vmware.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: automated trace output with gdb
Date: Fri, 31 Oct 2008 08:20:00 -0000 [thread overview]
Message-ID: <5cfa99000810301045q60743d8ata5d687430f363792@mail.gmail.com> (raw)
In-Reply-To: <4908D5BA.8000103@vmware.com>
Michael,
I'd be glad to contribute, but I'm not sure I know the infrastructure
of gdb well enough to do it correctly. Any pointers on what would be
involved in making a change like this?
Ed
On Wed, Oct 29, 2008 at 2:29 PM, Michael Snyder <msnyder@vmware.com> wrote:
> Edward Peschko wrote:
>
>> (gdb) set pagination off
>
> FYI, you can also use "set height 0" in place of the above.
>
>>
>> I don't know - all in all, IMO this should be a feature of gdb itself,
>> just for simplicity's sake, and to avoid the overhead of the scripting
>> language. I'm just guessing, but I'd bet that if this was done in a
>> tight loop, it would be an order of magnitude faster..
>
> Well -- it's an open source project, we welcome contributions.
>
>
WARNING: multiple messages have this Message-ID
From: "Edward Peschko" <horos11@gmail.com>
To: "Michael Snyder" <msnyder@vmware.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: automated trace output with gdb
Date: Thu, 30 Oct 2008 21:49:00 -0000 [thread overview]
Message-ID: <5cfa99000810301045q60743d8ata5d687430f363792@mail.gmail.com> (raw)
Message-ID: <20081030214900.POHzdFLFYl6js_Ty7oSZnMO1FAQX9ubiAoRZL4b2DPk@z> (raw)
In-Reply-To: <4908D5BA.8000103@vmware.com>
Michael,
I'd be glad to contribute, but I'm not sure I know the infrastructure
of gdb well enough to do it correctly. Any pointers on what would be
involved in making a change like this?
Ed
On Wed, Oct 29, 2008 at 2:29 PM, Michael Snyder <msnyder@vmware.com> wrote:
> Edward Peschko wrote:
>
>> (gdb) set pagination off
>
> FYI, you can also use "set height 0" in place of the above.
>
>>
>> I don't know - all in all, IMO this should be a feature of gdb itself,
>> just for simplicity's sake, and to avoid the overhead of the scripting
>> language. I'm just guessing, but I'd bet that if this was done in a
>> tight loop, it would be an order of magnitude faster..
>
> Well -- it's an open source project, we welcome contributions.
>
>
next prev parent reply other threads:[~2008-10-30 22:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 7:02 Edward Peschko
2008-10-29 17:17 ` Michael Snyder
2008-10-29 17:58 ` Edward Peschko
2008-10-29 18:03 ` Michael Snyder
2008-10-29 19:03 ` Edward Peschko
2008-10-29 21:35 ` Michael Snyder
2008-10-31 8:20 ` Edward Peschko [this message]
2008-10-30 21:49 ` Edward Peschko
2008-10-31 12:43 ` Jeremy Bennett
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=5cfa99000810301045q60743d8ata5d687430f363792@mail.gmail.com \
--to=horos11@gmail.com \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.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