From: Tom Tromey <tromey@redhat.com>
To: "Tiago Stürmer Daitx" <tdaitx@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org, emachado@linux.vnet.ibm.com,
Ulrich.Weigand@de.ibm.com
Subject: Re: [PATCH] Fix handling of #include files during prologue skipping
Date: Wed, 23 Jan 2013 20:44:00 -0000 [thread overview]
Message-ID: <87vcantyt6.fsf@fleche.redhat.com> (raw)
In-Reply-To: <51004922.0VYgHGakDPQGcTqV%tdaitx@linux.vnet.ibm.com> ("Tiago =?utf-8?Q?St=C3=BCrmer?= Daitx"'s message of "Wed, 23 Jan 2013 14:33:38 -0600")
>>>>> "Tiago" == Tiago Stürmer Daitx <tdaitx@linux.vnet.ibm.com> writes:
Tiago> 2013-01-23 Ulrich Weigand <uweigand@de.ibm.com>
Tiago> * symtab.c (skip_prologue_using_sal): Consider a file
Tiago> change the same as an increased line number
Tiago> gdb/testsuite/ChangeLog
Tiago> 2013-01-23 Tiago Stürmer Daitx <tdaitx@linux.vnet.ibm.com>
Tiago> * gdb.base/prologue-include.c: New file.
Tiago> * gdb.base/prologue-include.exp: New file.
Tiago> * gdb.base/prologue-include.h: New file.
This version looks good to me, thanks.
Tom
next prev parent reply other threads:[~2013-01-23 20:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 20:34 Tiago Stürmer Daitx
2013-01-23 20:44 ` Tom Tromey [this message]
2013-01-24 0:52 ` Yao Qi
2013-01-24 3:19 ` Tiago Stürmer Daitx
2013-01-24 3:42 ` Yao Qi
2013-01-24 6:23 ` Joel Brobecker
2013-01-24 11:13 ` Pedro Alves
2013-01-24 12:56 ` Ulrich Weigand
2013-01-24 13:11 ` Tiago Stürmer Daitx
2013-01-24 14:28 ` Tiago Stürmer Daitx
2013-01-24 15:01 ` Tiago Stürmer Daitx
2013-01-24 15:12 ` Tom Tromey
2013-01-24 20:43 ` Tiago Stürmer Daitx
-- strict thread matches above, loose matches on Subject: below --
2013-01-23 18:39 Tiago Stürmer Daitx
2013-01-23 19:30 ` Ulrich Weigand
2013-01-23 19:38 ` Tom Tromey
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=87vcantyt6.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=emachado@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=tdaitx@linux.vnet.ibm.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