|
From: Julian S. <js...@ac...> - 2004-08-30 18:22:39
|
Ok, folks, this is the final call for 2.2.0. I've updated NEWS, hopefully appropriately. Let me know if there's anything else to go in. Nick, I'm assuming you'll commit your fix for #78765. I'll update docs, version numbers, etc, later this evening. If tonight's autobuilds don't show any unusual breakage, I'll tag the tree tomorrow morning, and run with that. J |
|
From: Bob F. <bfr...@si...> - 2004-08-30 18:26:24
|
On Mon, 30 Aug 2004, Julian Seward wrote: > > Ok, folks, this is the final call for 2.2.0. I've updated NEWS, > hopefully appropriately. Let me know if there's anything else > to go in. Nick, I'm assuming you'll commit your fix for #78765. > I'll update docs, version numbers, etc, later this evening. If the timer_* support code is ok, it would be cool if it made it into the release. Bob ====================================== Bob Friesenhahn bfr...@si... http://www.simplesystems.org/users/bfriesen |
|
From: Tom H. <th...@cy...> - 2004-08-30 18:55:19
|
In message <Pin...@bl...>
Bob Friesenhahn <bfr...@si...> wrote:
> On Mon, 30 Aug 2004, Julian Seward wrote:
>
> >
> > Ok, folks, this is the final call for 2.2.0. I've updated NEWS,
> > hopefully appropriately. Let me know if there's anything else
> > to go in. Nick, I'm assuming you'll commit your fix for #78765.
> > I'll update docs, version numbers, etc, later this evening.
>
> If the timer_* support code is ok, it would be cool if it made it into
> the release.
If people are happy for it to go in - it's only some system call
wrapper so can't break much - then I'll commit it.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: Nicholas N. <nj...@ca...> - 2004-08-30 19:24:35
|
On Mon, 30 Aug 2004, Tom Hughes wrote: >>> Ok, folks, this is the final call for 2.2.0. I've updated NEWS, >>> hopefully appropriately. Let me know if there's anything else >>> to go in. Nick, I'm assuming you'll commit your fix for #78765. Done. >>> I'll update docs, version numbers, etc, later this evening. >> >> If the timer_* support code is ok, it would be cool if it made it into >> the release. > > If people are happy for it to go in - it's only some system call > wrapper so can't break much - then I'll commit it. Fine by me. N |
|
From: Eric E. <eri...@fr...> - 2004-08-30 19:19:48
|
Julian Seward wrote: > Ok, folks, this is the final call for 2.2.0. I've updated NEWS, Mmmmm. Still my dwarf2 updates + small updates for Valgui ? Never mind I try. Could people who would be interested but had no time to have a look at it send me an email ? Did some people have a look, I didn't get many feedback (but didn't ask for, though....) Now it's gonna be a bit late :-P Cheers -- Eric |
|
From: Julian S. <js...@ac...> - 2004-08-30 23:56:21
|
On Monday 30 August 2004 20:19, Eric Estievenart wrote: > Julian Seward wrote: > > Ok, folks, this is the final call for 2.2.0. I've updated NEWS, > > Mmmmm. Still my dwarf2 updates + small updates for Valgui ? > Never mind I try. Could people who would be interested > but had no time to have a look at it send me an email ? > > Did some people have a look, I didn't get many feedback > (but didn't ask for, though....) Eric I think your Valgui patches have created some interesting discussions and thinking a bit about GUIs in the future, and that's a good thing. But at the moment there doesn't seem to be enough support to put your patch into the tree. I suspect the GUI issue is something that will be returned to in the future, though. J |
|
From: Eric E. <eri...@fr...> - 2004-08-31 00:44:35
|
Julian Seward wrote: > Eric > > I think your Valgui patches have created some interesting discussions > and thinking a bit about GUIs in the future, and that's a good thing. > But at the moment there doesn't seem to be enough support to put your > patch into the tree. I suspect the GUI issue is something that will > be returned to in the future, though. You're right. I'll work on my release, keeping the patch as-is (with extra string for valgrind --version). I hope that there will be enough feedback after my first initial release. Maybe I'll not miss the next Valgrind release once more... Could we at least statuate on one thing: the name/format of the argument triggering the 'special' output ? For now I'm using --fmt=valgui, but --format=valgui may be more appropriate/explicit. Not that I really care, but I'd rather have things fixed definitely... Cheers -- Eric |
|
From: Nicholas N. <nj...@ca...> - 2004-08-31 09:38:39
|
On Tue, 31 Aug 2004, Eric Estievenart wrote: >> I think your Valgui patches have created some interesting discussions >> and thinking a bit about GUIs in the future, and that's a good thing. >> But at the moment there doesn't seem to be enough support to put your >> patch into the tree. I suspect the GUI issue is something that will be >> returned to in the future, though. > > You're right. I'll work on my release, keeping the patch as-is > (with extra string for valgrind --version). > I hope that there will be enough feedback after my first initial > release. Maybe I'll not miss the next Valgrind release once more... > > Could we at least statuate on one thing: the name/format of the > argument triggering the 'special' output ? > > For now I'm using --fmt=valgui, but --format=valgui may be more > appropriate/explicit. Not that I really care, but I'd rather > have things fixed definitely... I would go with --format. However, I don't think a command-line option is the best way to go with this in general. I think some way of customing error messages (eg. with some kind of format string, maybe specified in a file) should occur in the future, and that this would be the best way of getting the changes you require. This would be far more flexible than having a bunch of --format=XXX options, which pre-choose the possible output formats. It would also be the way of addressing the issues you raised in your message "Logging interface" (eg. producing HTML). Your experience with Valgui will be useful for this, for knowing what kinds of thing people might/might not want in the error messages. But it won't happen straight away. N |
|
From: Jeroen N. W. <jn...@xs...> - 2004-08-30 21:33:40
|
On Valgrind-CVS, updated Aug 30 (today) 23:28 CEST, I get compile errors: valgrind/coregrind/vg_syscalls.c: In function `before_timer_settime': valgrind/coregrind/vg_syscalls.c:5782: error: invalid application of `sizeof' to an incomplete type valgrind/coregrind/vg_syscalls.c:5785: error: invalid application of `sizeof' to an incomplete type valgrind/coregrind/vg_syscalls.c: In function `after_timer_settime': valgrind/coregrind/vg_syscalls.c:5792: error: invalid application of `sizeof' to an incomplete type valgrind/coregrind/vg_syscalls.c: In function `before_timer_gettime': valgrind/coregrind/vg_syscalls.c:5799: error: invalid application of `sizeof' to an incomplete type valgrind/coregrind/vg_syscalls.c: In function `after_timer_gettime': valgrind/coregrind/vg_syscalls.c:5805: error: invalid application of `sizeof' to an incomplete type The problem is in 'struct vki_itimerspec'. In what file is this struct defined? Jeroen. > > Ok, folks, this is the final call for 2.2.0. I've updated NEWS, > hopefully appropriately. Let me know if there's anything else > to go in. Nick, I'm assuming you'll commit your fix for #78765. > I'll update docs, version numbers, etc, later this evening. > > If tonight's autobuilds don't show any unusual breakage, I'll > tag the tree tomorrow morning, and run with that. > > J > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |
|
From: Tom H. <th...@cy...> - 2004-08-30 21:42:11
|
In message <896...@we...>
"Jeroen N. Witmond" <jn...@xs...> wrote:
> On Valgrind-CVS, updated Aug 30 (today) 23:28 CEST, I get compile errors:
>
> valgrind/coregrind/vg_syscalls.c: In function `before_timer_settime':
> valgrind/coregrind/vg_syscalls.c:5782: error: invalid application of
> `sizeof' to an incomplete type
> valgrind/coregrind/vg_syscalls.c:5785: error: invalid application of
> `sizeof' to an incomplete type
> valgrind/coregrind/vg_syscalls.c: In function `after_timer_settime':
> valgrind/coregrind/vg_syscalls.c:5792: error: invalid application of
> `sizeof' to an incomplete type
> valgrind/coregrind/vg_syscalls.c: In function `before_timer_gettime':
> valgrind/coregrind/vg_syscalls.c:5799: error: invalid application of
> `sizeof' to an incomplete type
> valgrind/coregrind/vg_syscalls.c: In function `after_timer_gettime':
> valgrind/coregrind/vg_syscalls.c:5805: error: invalid application of
> `sizeof' to an incomplete type
>
> The problem is in 'struct vki_itimerspec'. In what file is this struct
> defined?
It's in include/vg_kerneliface.h and it was committed about half an
hour after the change to vg_syscalls.c because I forgot it at first.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: Jeroen N. W. <jn...@xs...> - 2004-08-30 22:14:21
|
Then I'm afraid something went wrong with that commit. I cannot find 'struct vki_itimerspec' in file include/vg_kerneliface.h, and http://webcvs.kde.org/cgi-bin/cvsweb.cgi/valgrind/include/?sortby=date shows the file to be 2 weeks old. Jeroen. > In message <896...@we...> > "Jeroen N. Witmond" <jn...@xs...> wrote: > >> On Valgrind-CVS, updated Aug 30 (today) 23:28 CEST, I get compile >> errors: >> >> valgrind/coregrind/vg_syscalls.c: In function `before_timer_settime': >> valgrind/coregrind/vg_syscalls.c:5782: error: invalid application of >> `sizeof' to an incomplete type >> valgrind/coregrind/vg_syscalls.c:5785: error: invalid application of >> `sizeof' to an incomplete type >> valgrind/coregrind/vg_syscalls.c: In function `after_timer_settime': >> valgrind/coregrind/vg_syscalls.c:5792: error: invalid application of >> `sizeof' to an incomplete type >> valgrind/coregrind/vg_syscalls.c: In function `before_timer_gettime': >> valgrind/coregrind/vg_syscalls.c:5799: error: invalid application of >> `sizeof' to an incomplete type >> valgrind/coregrind/vg_syscalls.c: In function `after_timer_gettime': >> valgrind/coregrind/vg_syscalls.c:5805: error: invalid application of >> `sizeof' to an incomplete type >> >> The problem is in 'struct vki_itimerspec'. In what file is this struct >> defined? > > It's in include/vg_kerneliface.h and it was committed about half an > hour after the change to vg_syscalls.c because I forgot it at first. > > Tom > > -- > Tom Hughes (th...@cy...) > Software Engineer, Cyberscience Corporation > http://www.cyberscience.com/ > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |
|
From: Tom H. <th...@cy...> - 2004-08-30 22:17:39
|
In message <240...@we...>
"Jeroen N. Witmond" <jn...@xs...> wrote:
> Then I'm afraid something went wrong with that commit. I cannot find
> 'struct vki_itimerspec' in file include/vg_kerneliface.h, and
> http://webcvs.kde.org/cgi-bin/cvsweb.cgi/valgrind/include/?sortby=date
> shows the file to be 2 weeks old.
No, you're probably just looking at a mirror rather than the master
site - changes can take a while to propagate.
Try cvs.kde.org if you're using another site, and see if that has
the update or not. I've just updated one of my other checkouts from
that site and it definitely got the edit.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: Julian S. <js...@ac...> - 2004-08-30 23:35:33
|
On Monday 30 August 2004 23:17, Tom Hughes wrote: > In message <240...@we...> > > "Jeroen N. Witmond" <jn...@xs...> wrote: > > Then I'm afraid something went wrong with that commit. I cannot find > > 'struct vki_itimerspec' in file include/vg_kerneliface.h, and > > http://webcvs.kde.org/cgi-bin/cvsweb.cgi/valgrind/include/?sortby=date > > shows the file to be 2 weeks old. > > No, you're probably just looking at a mirror rather than the master > site - changes can take a while to propagate. Yeh, it's a propagation problem. I just cvs up'd and it all works for me. J |