* [RFC] Add ARI directory to gdb sources
@ 2012-05-16 7:42 Pierre Muller
2012-05-16 14:44 ` Joel Brobecker
0 siblings, 1 reply; 6+ messages in thread
From: Pierre Muller @ 2012-05-16 7:42 UTC (permalink / raw)
To: gdb-patches
We recently had a discussion about integrating gdb_ari.sh script
into gdb sources directly.
See:
http://sourceware.org/ml/gdb-patches/2012-04/msg00834.html
Currently the ARI (Awk Regression Index)
script is a separate cvs checkout
and is used to generate three type of ARI reports:
Last release ARI:
http://sourceware.org/gdb/download/ari/
generated normally in the release process.
daily run for current cvs trunk:
http://sourceware.org/gdb/current/ari/
daily run for most recent branch:
http://sourceware.org/gdb/ari/
The idea behind moving gdb_ari.sh script into gdb sources
would be:
1) Be able to adapt this script to changes in the gdb sources.
Example: Currently, there are 14 types of critical bugs
(corresponding to previously eliminated problems that resurfaced).
These are mostly due to some functions that should not generally
be used in the gdb sources (like xasprintf function)
but are present at specific locations:
BEGIN { doc["xasprintf"] = "\
Do not use xasprintf(), instead use xstrprintf"
fix("xasprintf", "gdb/defs.h", 1)
fix("xasprintf", "gdb/utils.c", 1)
category["xasprintf"] = ari_regression
}
/(^|[^_[:alnum:]])xasprintf[[:space:]]*\(/ {
fail("xasprintf")
}
This means that xasprintf function should appear
only two type in the whole gdb sources,
once in defs.gh and once in utils.c.
But recent changes (moves of some functions to common
subdirectory), lead to the fact that xasprintf is now
referenced in common/common-utils.h and common/common-utils.c
This is of course not a real problem, but changing this
in the gdb_ari.sh script would mean that this script would
give wrong information if run on older gdb sources.
2) The second reason was to allow developers or any person
that wants to analyze gdb sources to run this script.
The question of the location where we should add this script in gdb source
arose.
Joel suggested to put it directly into
gdb directory.
But after looking at the suggestion, it appears
that you can't just use gdb_ari.sh alone,
the update-web-ari script also uses gdb_find.sh script for instance,
and a modified version of this update-web-air should probably also
be added.
Thus I would rather suggest to add a new directory called ari.
Suggestions and comments most welcomed,
Pierre Muller
GDB pascal language maintainer
writing as unofficial ARI maitainer
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [RFC] Add ARI directory to gdb sources
2012-05-16 7:42 [RFC] Add ARI directory to gdb sources Pierre Muller
@ 2012-05-16 14:44 ` Joel Brobecker
2012-05-18 21:17 ` Sergio Durigan Junior
0 siblings, 1 reply; 6+ messages in thread
From: Joel Brobecker @ 2012-05-16 14:44 UTC (permalink / raw)
To: Pierre Muller; +Cc: gdb-patches
> The question of the location where we should add this script in gdb
> source arose. Joel suggested to put it directly into gdb directory.
Yeah, I didn't say it, but I agree it was a poor suggestion,
especially in light of:
> But after looking at the suggestion, it appears that you can't just
> use gdb_ari.sh alone, the update-web-ari script also uses
> gdb_find.sh script for instance, and a modified version of this
> update-web-air should probably also be added.
Here's what I think: Everything that generates is required to generate
the HTML code should be moved to the GDB directory. gdb/ari/ seems
fine to me, but others might want to comment. Unless the location
is critical to the implementation, which I hope it won't be, you
can start working on the move and submit patches. It should be
relatively easy to change the names if other suggestions appear.
On a user-interface level, it would be nice if the script that generates
the HTML was callable from out of tree, a little like configure.
I could create the HTML is a directory called "ari" located in
the current directory, for instance...
> writing as unofficial ARI maitainer
As far as I am concerned, you are the official ARI Maintainer :).
We'll make that official-official as soon as the code is moved
to the GDB repository by adding a section in the MAINTAINERS file.
--
Joel
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [RFC] Add ARI directory to gdb sources
2012-05-16 14:44 ` Joel Brobecker
@ 2012-05-18 21:17 ` Sergio Durigan Junior
2012-05-18 22:00 ` Joel Brobecker
0 siblings, 1 reply; 6+ messages in thread
From: Sergio Durigan Junior @ 2012-05-18 21:17 UTC (permalink / raw)
To: Joel Brobecker; +Cc: Pierre Muller, gdb-patches
On Wednesday, May 16 2012, Joel Brobecker wrote:
>> But after looking at the suggestion, it appears that you can't just
>> use gdb_ari.sh alone, the update-web-ari script also uses
>> gdb_find.sh script for instance, and a modified version of this
>> update-web-air should probably also be added.
>
> Here's what I think: Everything that generates is required to generate
> the HTML code should be moved to the GDB directory. gdb/ari/ seems
> fine to me, but others might want to comment. Unless the location
> is critical to the implementation, which I hope it won't be, you
> can start working on the move and submit patches. It should be
> relatively easy to change the names if other suggestions appear.
Pierre showed up in IRC and mentioned that someone suggested
`gdb/contrib'. I could not find the thread/message, but I support this
idea FWIW. `gdb/contrib/ari' would be good, then.
My rationale is that ARI is not part of GDB as a program nor distributed
with it, so creating `gdb/ari' would perhaps confuse people because
there are other directories there like `gdb/mi' or `gdb/cli'.
My 2 cents.
--
Sergio
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [RFC] Add ARI directory to gdb sources
2012-05-18 21:17 ` Sergio Durigan Junior
@ 2012-05-18 22:00 ` Joel Brobecker
2012-05-18 22:17 ` Sergio Durigan Junior
0 siblings, 1 reply; 6+ messages in thread
From: Joel Brobecker @ 2012-05-18 22:00 UTC (permalink / raw)
To: Sergio Durigan Junior; +Cc: Pierre Muller, gdb-patches
> Pierre showed up in IRC and mentioned that someone suggested
> `gdb/contrib'. I could not find the thread/message, but I support this
> idea FWIW. `gdb/contrib/ari' would be good, then.
>
> My rationale is that ARI is not part of GDB as a program nor distributed
> with it, so creating `gdb/ari' would perhaps confuse people because
> there are other directories there like `gdb/mi' or `gdb/cli'.
That was Doug Evans.
I have no issues with contrib/ari, and I kind of like it better too.
I do feel the need to correct that the new scripts will be part of GDB,
and thus will be distributed with it as well.
--
Joel
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [RFC] Add ARI directory to gdb sources
2012-05-18 22:00 ` Joel Brobecker
@ 2012-05-18 22:17 ` Sergio Durigan Junior
0 siblings, 0 replies; 6+ messages in thread
From: Sergio Durigan Junior @ 2012-05-18 22:17 UTC (permalink / raw)
To: Joel Brobecker; +Cc: Pierre Muller, gdb-patches
On Friday, May 18 2012, Joel Brobecker wrote:
> I have no issues with contrib/ari, and I kind of like it better too.
> I do feel the need to correct that the new scripts will be part of GDB,
> and thus will be distributed with it as well.
Duh. Thank you for this correction, now that I've come to think of it,
it makes total sense.
So, Pierre, does that answer the question? I guess you're free to go
with `gdb/contrib/ari', then.
Regards,
--
Sergio
^ permalink raw reply [flat|nested] 6+ messages in thread
[parent not found: <48797.7718854838$1337154172@news.gmane.org>]
end of thread, other threads:[~2012-05-18 22:17 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-05-16 7:42 [RFC] Add ARI directory to gdb sources Pierre Muller
2012-05-16 14:44 ` Joel Brobecker
2012-05-18 21:17 ` Sergio Durigan Junior
2012-05-18 22:00 ` Joel Brobecker
2012-05-18 22:17 ` Sergio Durigan Junior
[not found] <48797.7718854838$1337154172@news.gmane.org>
2012-05-16 14:50 ` Tom Tromey
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox