public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Martin M. Hunt" <hunt@redhat.com>
To: Fernando Nasser <fnasser@cygnus.com>
Cc: <insight@sources.redhat.com>
Subject: Re: [RFC] patch to fix finding sources
Date: Tue, 06 Feb 2001 13:30:00 -0000	[thread overview]
Message-ID: <Pine.SUN.4.33.0102061306510.5291-100000@rtl.cygnus.com> (raw)
In-Reply-To: <3A804953.75535BD3@cygnus.com>

Sorry about the brief comments and forgetting to add the changelog into
the email.  I have more time now, so I'll explain in more detail.

gdb_find_file checks for the existance of a source file on the development
host.  It is expected that many sources (particularly to shared libraries)
will not be found.  That is why I didn't like the idea that TCL_ERROR
would be returned forcing a catch to always be used.  Then you have to
either parse the error message to determine if a warning or eror dialog is
displayed, or always ignore it.  No big deal either way...

when you call full_lookup_symtab() you get a pointer to a symtab struct.
If that pointer is NULL, it is probably an error.  If the pointer is not
null, st->fullname will be null if there if the sources are not found.
So, your code needs changed around a bit to avoid dereferencing a null
pointer.

The real problem here is probably my comment on full_lookup_symtab() that
says it always sets symtab->filename.  Maybe we need a note that it will
be set to null is the sources are not available.

If you want to test yourself, my test case is not too difficult :^)

main()
{
	printf("Hello World\n");
}

compile, run gdb, try to step into printf.

Martin


On Tue, 6 Feb 2001, Fernando Nasser wrote:

> I have added a few bits to Martin's patch, but I don't have how to test it at the moment.  I would need Martin's help as he probably has the situation repeatable right now (which caused him to send the patch).
>
> I have attached the patch.
>
> --
> Fernando Nasser
> Red Hat - Toronto                       E-Mail:  fnasser@redhat.com
> 2323 Yonge Street, Suite #300
> Toronto, Ontario   M4P 2C9

  reply	other threads:[~2001-02-06 13:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-06  8:50 Martin M. Hunt
2001-02-06  9:23 ` Fernando Nasser
2001-02-06 10:58   ` Fernando Nasser
2001-02-06 13:30     ` Martin M. Hunt [this message]
2001-02-06 14:57       ` Fernando Nasser
2001-02-06 15:05       ` Fernando Nasser
2001-02-06 15:22     ` Fernando Nasser
2001-02-06 16:10       ` Fernando Nasser
2001-02-06 17:05 ` Fernando Nasser

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.SUN.4.33.0102061306510.5291-100000@rtl.cygnus.com \
    --to=hunt@redhat.com \
    --cc=fnasser@cygnus.com \
    --cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).