public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@cygnus.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Insight List <insight@sourceware.cygnus.com>
Subject: Re: Patch ping
Date: Wed, 17 Oct 2001 13:25:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.33.0110171138400.11927-100000@makita.cygnus.com> (raw)
In-Reply-To: <87k7xukxdc.fsf@creche.redhat.com>

On 17 Oct 2001, Tom Tromey wrote:

> I have a couple pending patches.  If you don't want pings like this,
> tell me and I won't send them.

By all means: remind me when I forget!

> A simple fix for the M-b binding:
>
>     http://sources.redhat.com/ml/insight/2001-q4/msg00058.html

I thought that I approved this long, long ago? Hmmm. Don't see anything.
Please commit.

> Load sessions at startup and in response to the `file' command:
>
>     http://sources.redhat.com/ml/insight/2001-q4/msg00056.html

I played with this a bit, and I could only find two small problems, which
I am not sure really require fixing. Here's what I tried...

$ gdb/gdb gdb/gdb <WORKED>
$ gdb/gdb ~/sources/linux/gdb <WORKED>
$ ./gdb ./gdb <DID NOT WORK>
$ gdb/gdb ../linux/gdb/gdb <DID NOT WORK>

In all cases, the same gdb executable was targetted.

(I was pleasantly suprised, though, that using File->Close did
everything it needed to do.)

I don't know if this can be easily fixed, or if we even want to, but it
seems (at worst), that we could do something like:

proc SESSION_exe {exe_name} {
  global tcl_platform

  # get real directory for gdb_exe_name
  if {[string compare $tcl_platform(platform) "windows"] == 0} {
    set file [ide_cygwin_path to_win32 $exe_name]
  } else {
    set file $exe_name
  }
  set dir [file dirname $file]
  set cdir [pwd]
  cd $dir
  set dir [pwd]
  cd $cdir
  return [file join $dir [file tail $file]]
}

proc SESSION_exe_key {exe_name} {
  set name [SESSION_exe $exe_name]
  return gdb/session/$name
}

Putting SESSION_exe_key in a session_load, session_save, and
session_notice_file_change should help us to fix these problems.

?
Keith


  reply	other threads:[~2001-10-17 13:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-17  9:52 Tom Tromey
2001-10-17 13:25 ` Keith Seitz [this message]
2001-10-17 16:29   ` Tom Tromey
  -- strict thread matches above, loose matches on Subject: below --
2012-04-16  9:16 Roland Schwingel
2006-01-23 17:58 Andrew STUBBS
2006-01-24  1:35 ` Keith Seitz
2006-01-24 11:33   ` Andrew STUBBS
2002-01-05 12:59 Tom Tromey
2002-01-07  9:32 ` Keith Seitz
2002-01-08 11:33   ` Tom Tromey
     [not found] <87snan6n7u.fsf@creche.redhat.com>
2001-10-10  9:28 ` Elena Zannoni
2001-10-10 10:01   ` Keith Seitz
2001-12-07 10:00     ` Keith Seitz
2001-10-11 10:35   ` Tom Tromey
2001-12-08 19:57     ` Tom Tromey
2001-12-07  8:14   ` Elena Zannoni

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=Pine.GSO.4.33.0110171138400.11927-100000@makita.cygnus.com \
    --to=keiths@cygnus.com \
    --cc=insight@sourceware.cygnus.com \
    --cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).