public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Dave Korn" <dave.korn@artimi.com>
To: "'Torsten Mohr'" <tmohr@s.netic.de>, 	<insight@sourceware.org>
Subject: RE: would this be an improvement?
Date: Thu, 08 Jun 2006 14:39:00 -0000	[thread overview]
Message-ID: <00bf01c68b09$64e9faa0$a501a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <200606081608.38613.tmohr@s.netic.de>

On 08 June 2006 15:09, Torsten Mohr wrote:

> Whatever i do, i _have_ _to_ change the size of that main
> window to make the _other_ toolbar appear where i can select
> the function/file and the view of the source window (SOURCE,
> ASSEMBLY, MIXED, SRC+ASM).
> 
> Is it possible to make this one appear straight from the beginning?

http://sourceware.org/ml/insight/2006-q1/threads.html#00004
http://sourceware.org/ml/insight/2006-q1/threads.html#00009

It's a known bug.  The patch at 

http://sourceware.org/ml/insight/2006-q1/msg00009.html

works for me.

> One more thing, for a bug report i just had to describe the
> content of the stack window.
> Is there a way to mark all the entries and "copy" them?
> I don't know how much effort there is in generating a right-click
> popup menu "Select all" and generate a string from the single
> entries in the listbox.  I think some function like that could be
> useful for the other windows as well.
> At the moment the least error prone way to describe others the
> content is to make a screen shot.  Sending those around on a
> mailing list is mostly not appreciated.

  Actually, the best way is to issue the "bt" command in the console window,
from where you *can* cut and paste the output easily.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....

  reply	other threads:[~2006-06-08 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08 14:05 Torsten Mohr
2006-06-08 14:39 ` Dave Korn [this message]
2006-06-08 20:27   ` Torsten Mohr
2006-06-26 20:46     ` Keith Seitz

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='00bf01c68b09$64e9faa0$a501a8c0@CAM.ARTIMI.COM' \
    --to=dave.korn@artimi.com \
    --cc=insight@sourceware.org \
    --cc=tmohr@s.netic.de \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).