Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #59888 > unrolled thread
| Started by | gazelle@shell.xmission.com (Kenny McCormack) |
|---|---|
| First post | 2015-04-10 20:54 +0000 |
| Last post | 2015-04-18 08:11 -0700 |
| Articles | 20 on this page of 211 — 35 participants |
Back to article view | Back to comp.lang.c
Problems with va_list & friends... gazelle@shell.xmission.com (Kenny McCormack) - 2015-04-10 20:54 +0000
Re: Problems with va_list & friends... Andrew Cooper <amc96@cam.ac.uk> - 2015-04-10 22:36 +0100
Re: Problems with va_list & friends... Martin Shobe <martin.shobe@yahoo.com> - 2015-04-10 16:47 -0500
Re: Problems with va_list & friends... Robert Wessel <robertwessel2@yahoo.com> - 2015-04-10 16:50 -0500
Re: Problems with va_list & friends... Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-04-10 15:33 -0700
Re: Problems with va_list & friends... Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-04-10 23:02 +0100
Re: Problems with va_list & friends... Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-04-11 03:00 +0000
Re: Problems with va_list & friends... gazelle@shell.xmission.com (Kenny McCormack) - 2015-04-11 03:18 +0000
Re: Problems with va_list & friends... Richard Damon <Richard@Damon-Family.org> - 2015-04-11 00:04 -0400
Re: Problems with va_list & friends... Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-04-11 16:02 +0000
Re: Problems with va_list & friends... Ian Collins <ian-news@hotmail.com> - 2015-04-12 08:27 +1200
Re: Problems with va_list & friends... Richard Damon <Richard@Damon-Family.org> - 2015-04-11 17:48 -0400
Re: Problems with va_list & friends... Robert Wessel <robertwessel2@yahoo.com> - 2015-04-12 01:06 -0500
Re: Problems with va_list & friends... Martin Shobe <martin.shobe@yahoo.com> - 2015-04-11 10:49 -0500
Re: Problems with va_list & friends... Lőrinczy Zsigmond <nospam@for.me> - 2015-04-12 17:58 +0200
Re: Problems with va_list & friends... Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-04-13 17:31 +0000
Re: Problems with va_list & friends... gazelle@shell.xmission.com (Kenny McCormack) - 2015-04-13 17:48 +0000
Re: Problems with va_list & friends... Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-04-14 20:26 +0000
Re: Problems with va_list & friends... Noob <root@127.0.0.1> - 2015-04-14 22:58 +0200
Re: Problems with va_list & friends... Philipp Klaus Krause <pkk@spth.de> - 2015-04-16 13:08 +0200
Re: Problems with va_list & friends... Les Cargill <lcargill99@comcast.com> - 2015-04-16 12:14 -0500
Re: Problems with va_list & friends... gazelle@shell.xmission.com (Kenny McCormack) - 2015-04-16 17:18 +0000
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-16 18:43 +0100
Re: Problems with va_list & friends... Les Cargill <lcargill99@comcast.com> - 2015-04-16 21:03 -0500
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-16 23:38 -0400
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-17 07:39 +0100
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-17 13:31 -0500
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-17 14:46 -0400
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-18 11:46 -0700
Re: Problems with va_list & friends... Keith Thompson <kst-u@mib.org> - 2015-04-18 15:35 -0700
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-22 10:57 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-19 11:58 +0100
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-20 10:50 -0500
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-20 17:55 +0100
Re: Problems with va_list & friends... Les Cargill <lcargill99@comcast.com> - 2015-04-17 23:01 -0500
Re: Problems with va_list & friends... Robert Wessel <robertwessel2@yahoo.com> - 2015-04-18 00:24 -0500
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-18 07:50 -0400
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-18 11:56 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-19 14:59 +0100
Re: Problems with va_list & friends... Les Cargill <lcargill99@comcast.com> - 2015-04-19 11:47 -0500
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-19 18:44 +0100
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-19 18:34 -0400
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-20 01:42 -0700
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-20 08:14 -0400
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-20 10:30 -0700
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-20 13:56 -0400
Re: Problems with va_list & friends... Ian Pilcher <arequipeno@gmail.com> - 2015-04-20 18:39 -0500
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-23 12:37 -0700
Re: Problems with va_list & friends... Les Cargill <lcargill99@comcast.com> - 2015-04-23 20:25 -0500
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-24 07:58 -0700
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-24 12:58 -0500
Re: Problems with va_list & friends... Les Cargill <lcargill99@comcast.com> - 2015-04-24 22:13 -0500
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-28 13:05 -0700
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-30 08:40 -0500
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-05-01 08:40 -0700
Re: Problems with va_list & friends... Les Cargill <lcargill99@comcast.com> - 2015-05-03 11:42 -0500
Re: Problems with va_list & friends... Ian Collins <ian-news@hotmail.com> - 2015-05-04 17:43 +1200
Re: Problems with va_list & friends... Les Cargill <lcargill99@comcast.com> - 2015-05-04 07:34 -0500
Re: Problems with va_list & friends... Phil Carmody <pc+usenet@asdf.org> - 2015-05-08 17:12 +0300
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-05-10 07:40 -0700
Re: Problems with va_list & friends... Keith Thompson <kst-u@mib.org> - 2015-05-04 08:49 -0700
Re: Problems with va_list & friends... Les Cargill <lcargill99@comcast.com> - 2015-05-04 12:23 -0500
Re: Problems with va_list & friends... Les Cargill <lcargill99@comcast.com> - 2015-04-20 07:49 -0500
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-20 14:27 +0100
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-20 09:39 -0500
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-20 17:48 +0100
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-20 15:58 -0500
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-20 22:25 +0100
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-20 13:22 -0400
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-20 11:15 -0700
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-20 15:02 -0400
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-20 12:51 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-20 21:17 +0100
Re: Problems with va_list & friends... Keith Thompson <kst-u@mib.org> - 2015-04-20 16:09 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-21 00:33 +0100
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-20 16:26 -0400
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-20 15:46 -0700
Re: Problems with va_list & friends... Keith Thompson <kst-u@mib.org> - 2015-04-20 16:17 -0700
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-21 07:43 -0700
Re: Problems with va_list & friends... Keith Thompson <kst-u@mib.org> - 2015-04-21 08:06 -0700
Re: Problems with va_list & friends... Philip Lantz <prl@canterey.us> - 2015-04-22 21:55 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-20 20:04 +0100
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-20 13:22 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-20 21:42 +0100
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-20 16:58 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-21 01:16 +0100
Re: Problems with va_list & friends... Melzzzzz <mel@zzzzz.com> - 2015-04-21 02:19 +0200
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-20 23:14 -0700
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-21 11:47 -0400
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-22 00:13 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-22 08:36 +0100
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-22 03:15 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-22 11:52 +0100
Re: Problems with va_list & friends... Öö Tiib <ootiib@hot.ee> - 2015-04-22 09:04 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-22 17:14 +0100
Re: Problems with va_list & friends... Keith Thompson <kst-u@mib.org> - 2015-04-20 15:24 -0700
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-21 00:24 -0500
Re: Problems with va_list & friends... raltbos@xs4all.nl (Richard Bos) - 2015-04-21 09:33 +0000
Re: Problems with va_list & friends... gazelle@shell.xmission.com (Kenny McCormack) - 2015-04-21 11:57 +0000
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-21 10:22 -0500
The Metric system (Was: Problems with va_list & friends...) gazelle@shell.xmission.com (Kenny McCormack) - 2015-04-21 15:38 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Greg Martin <greg.at.softsprocket@dot.com> - 2015-04-21 15:58 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Bartc <bc@freeuk.com> - 2015-04-21 18:09 +0100
Re: The Metric system (Was: Problems with va_list & friends...) Greg Martin <greg.at.softsprocket@dot.com> - 2015-04-21 17:42 +0000
Re: The Metric system (Was: Problems with va_list & friends...) David Brown <david.brown@hesbynett.no> - 2015-04-22 10:47 +0200
Re: The Metric system (Was: Problems with va_list & friends...) Ian Collins <ian-news@hotmail.com> - 2015-04-22 20:56 +1200
Re: The Metric system (Was: Problems with va_list & friends...) guinness.tony@gmail.com - 2015-04-22 03:53 -0700
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-04-22 11:01 -0500
Re: The Metric system (Was: Problems with va_list & friends...) gwowen <gwowen@gmail.com> - 2015-04-23 08:17 -0700
Re: The Metric system (Was: Problems with va_list & friends...) Richard Heathfield <rjh@cpax.org.uk> - 2015-04-22 10:21 +0100
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-04-22 11:17 -0500
Re: The Metric system (Was: Problems with va_list & friends...) David Kleinecke <dkleinecke@gmail.com> - 2015-04-22 09:59 -0700
Re: The Metric system (Was: Problems with va_list & friends...) Bartc <bc@freeuk.com> - 2015-04-22 18:48 +0100
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-04-22 14:35 -0500
Re: The Metric system Ben Bacarisse <ben.lists@bsb.me.uk> - 2015-04-22 21:22 +0100
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-25 09:58 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Bartc <bc@freeuk.com> - 2015-04-25 12:33 +0100
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-25 12:18 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Bartc <bc@freeuk.com> - 2015-04-25 13:51 +0100
Re: The Metric system (Was: Problems with va_list & friends...) David Brown <david.brown@hesbynett.no> - 2015-04-25 16:34 +0200
Re: The Metric system (Was: Problems with va_list & friends...) Bartc <bc@freeuk.com> - 2015-04-25 17:00 +0100
Re: The Metric system (Was: Problems with va_list & friends...) gazelle@shell.xmission.com (Kenny McCormack) - 2015-04-25 16:59 +0000
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-28 16:04 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-30 04:22 -0700
Re: The Metric system (Was: Problems with va_list & friends...) Martin Shobe <martin.shobe@yahoo.com> - 2015-04-30 09:27 -0500
Re: The Metric system (Was: Problems with va_list & friends...) Robert Wessel <robertwessel2@yahoo.com> - 2015-04-30 12:01 -0500
Re: The Metric system (Was: Problems with va_list & friends...) Bartc <bc@freeuk.com> - 2015-04-30 13:38 +0100
Re: The Metric system (Was: Problems with va_list & friends...) David Brown <david.brown@hesbynett.no> - 2015-04-25 16:36 +0200
Re: The Metric system (Was: Problems with va_list & friends...) Ian Collins <ian-news@hotmail.com> - 2015-04-26 08:20 +1200
Re: The Metric system (Was: Problems with va_list & friends...) "Bill Davy" <Bill@SynectixLtd.com> - 2015-04-25 21:33 +0100
Re: The Metric system (Was: Problems with va_list & friends...) David Brown <david.brown@hesbynett.no> - 2015-04-26 12:07 +0200
Re: The Metric system (Was: Problems with va_list & friends...) Richard Heathfield <rjh@cpax.org.uk> - 2015-04-26 14:22 +0100
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-26 15:44 +0000
Re: The Metric system (Was: Problems with va_list & friends...) James Kuyper <jameskuyper@verizon.net> - 2015-04-22 13:11 -0400
Re: The Metric system (Was: Problems with va_list & friends...) Robert Wessel <robertwessel2@yahoo.com> - 2015-04-22 17:05 -0500
Re: The Metric system (Was: Problems with va_list & friends...) James Kuyper <jameskuyper@verizon.net> - 2015-04-22 18:30 -0400
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-04-22 17:35 -0500
Re: The Metric system (Was: Problems with va_list & friends...) James Kuyper <jameskuyper@verizon.net> - 2015-04-22 19:15 -0400
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-04-23 11:05 -0500
Re: The Metric system (Was: Problems with va_list & friends...) James Kuyper <jameskuyper@verizon.net> - 2015-04-23 12:54 -0400
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-04-23 14:12 -0500
Re: The Metric system (Was: Problems with va_list & friends...) James Kuyper <jameskuyper@verizon.net> - 2015-04-23 15:50 -0400
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-04-23 16:43 -0500
Re: The Metric system (Was: Problems with va_list & friends...) James Kuyper <jameskuyper@verizon.net> - 2015-04-23 18:09 -0400
Re: The Metric system (Was: Problems with va_list & friends...) "Osmium" <r124c4u102@comcast.net> - 2015-04-22 13:15 -0500
Re: The Metric system (Was: Problems with va_list & friends...) gazelle@shell.xmission.com (Kenny McCormack) - 2015-04-22 19:17 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Richard Heathfield <rjh@cpax.org.uk> - 2015-04-22 20:48 +0100
Re: The Metric system (Was: Problems with va_list & friends...) "Osmium" <r124c4u102@comcast.net> - 2015-04-23 08:11 -0500
Re: The Metric system (Was: Problems with va_list & friends...) James Kuyper <jameskuyper@verizon.net> - 2015-04-23 12:58 -0400
Re: The Metric system (Was: Problems with va_list & friends...) Robert Wessel <robertwessel2@yahoo.com> - 2015-04-23 14:13 -0500
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-25 10:08 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-04-22 17:15 -0500
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-25 09:18 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-04-25 13:02 -0500
Re: The Metric system (Was: Problems with va_list & friends...) Richard Heathfield <rjh@cpax.org.uk> - 2015-04-26 14:26 +0100
Re: The Metric system (Was: Problems with va_list & friends...) Philip Lantz <prl@canterey.us> - 2015-05-03 11:48 -0700
Re: The Metric system (Was: Problems with va_list & friends...) Richard Heathfield <rjh@cpax.org.uk> - 2015-05-05 18:20 +0100
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-05-05 12:43 -0500
Re: The Metric system (Was: Problems with va_list & friends...) Bartc <bc@freeuk.com> - 2015-04-22 11:32 +0100
Re: The Metric system (Was: Problems with va_list & friends...) "Bill Davy" <Bill@SynectixLtd.com> - 2015-04-22 14:31 +0100
Re: The Metric system (Was: Problems with va_list & friends...) Ian Collins <ian-news@hotmail.com> - 2015-04-23 07:51 +1200
Re: The Metric system (Was: Problems with va_list & friends...) "Bill Davy" <Bill@SynectixLtd.com> - 2015-04-23 08:05 +0100
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-25 10:10 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Richard Heathfield <rjh@cpax.org.uk> - 2015-04-26 09:27 +0100
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-26 10:55 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Morris Dovey <mrdovey@iedu.com> - 2015-04-26 07:19 -0500
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-26 12:59 +0000
Re: The Metric system (Was: Problems with va_list & friends...) gwowen <gwowen@gmail.com> - 2015-04-28 07:07 -0700
Re: The Metric system (Was: Problems with va_list & friends...) Morris Dovey <mrdovey@iedu.com> - 2015-04-28 09:51 -0500
Re: The Metric system (Was: Problems with va_list & friends...) guinness.tony@gmail.com - 2015-04-28 08:04 -0700
Re: The Metric system (Was: Problems with va_list & friends...) Richard Heathfield <rjh@cpax.org.uk> - 2015-04-28 16:19 +0100
Re: The Metric system (Was: Problems with va_list & friends...) Les Cargill <lcargill99@comcast.com> - 2015-04-28 19:15 -0500
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-28 16:06 +0000
Re: The Metric system (Was: Problems with va_list & friends...) guinness.tony@gmail.com - 2015-04-28 09:39 -0700
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-28 16:51 +0000
Re: The Metric system (Was: Problems with va_list & friends...) guinness.tony@gmail.com - 2015-04-29 05:08 -0700
Re: The Metric system (Was: Problems with va_list & friends...) raltbos@xs4all.nl (Richard Bos) - 2015-04-29 13:47 +0000
Re: The Metric system (Was: Problems with va_list & friends...) James Kuyper <jameskuyper@verizon.net> - 2015-04-28 13:03 -0400
Re: The Metric system (Was: Problems with va_list & friends...) David Thompson <dave.thompson2@verizon.net> - 2015-05-10 12:24 -0400
Re: The Metric system (Was: Problems with va_list & friends...) gazelle@shell.xmission.com (Kenny McCormack) - 2015-04-21 18:12 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Greg Martin <greg.at.softsprocket@dot.com> - 2015-04-21 19:34 +0000
Re: The Metric system (Was: Problems with va_list & friends...) Stephen Sprunk <stephen@sprunk.org> - 2015-04-21 12:46 -0500
Re: The Metric system (Was: Problems with va_list & friends...) Ian Collins <ian-news@hotmail.com> - 2015-04-22 07:42 +1200
Re: The Metric system (Was: Problems with va_list & friends...) Greg Martin <greg.at.softsprocket@dot.com> - 2015-04-21 20:13 +0000
Re: The Metric system (Was: Problems with va_list & friends...) David Brown <david.brown@hesbynett.no> - 2015-04-22 10:52 +0200
Re: The Metric system (Was: Problems with va_list & friends...) Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-04-22 09:18 -0700
Re: Problems with va_list & friends... raltbos@xs4all.nl (Richard Bos) - 2015-04-21 22:25 +0000
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-23 15:59 -0500
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-23 11:51 -0700
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-23 11:26 -0700
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-20 16:15 -0500
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-20 17:23 -0400
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-20 13:17 -0400
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-20 15:26 -0500
Re: Problems with va_list & friends... Keith Thompson <kst-u@mib.org> - 2015-04-20 16:15 -0700
Re: Problems with va_list & friends... Stephen Sprunk <stephen@sprunk.org> - 2015-04-21 00:42 -0500
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-22 11:15 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-20 21:50 +0100
Re: Problems with va_list & friends... James Kuyper <jameskuyper@verizon.net> - 2015-04-20 17:04 -0400
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-18 08:22 -0700
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-19 18:23 +0100
Re: Problems with va_list & friends... Keith Thompson <kst-u@mib.org> - 2015-04-19 13:22 -0700
Re: Problems with va_list & friends... Robert Wessel <robertwessel2@yahoo.com> - 2015-04-19 21:51 -0500
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-20 10:01 +0100
Re: Problems with va_list & friends... Robert Wessel <robertwessel2@yahoo.com> - 2015-04-20 05:08 -0500
Re: Problems with va_list & friends... Richard Heathfield <rjh@cpax.org.uk> - 2015-04-20 11:37 +0100
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-23 20:13 -0700
Re: Problems with va_list & friends... Philipp Klaus Krause <pkk@spth.de> - 2015-04-18 09:15 +0200
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-18 12:13 -0700
Re: Problems with va_list & friends... Richard Damon <Richard@Damon-Family.org> - 2015-04-16 23:40 -0400
Re: Problems with va_list & friends... Tim Rentsch <txr@alumni.caltech.edu> - 2015-04-18 08:11 -0700
Page 1 of 11 [1] 2 3 … 11 Next page →
| From | gazelle@shell.xmission.com (Kenny McCormack) |
|---|---|
| Date | 2015-04-10 20:54 +0000 |
| Subject | Problems with va_list & friends... |
| Message-ID | <mg9dak$ro0$1@news.xmission.com> |
Subtitle: Yes, Kenny posts something substantive...
I'm getting a strange result with va_list & friends. I've used this stuff
in the past, so I'm really perplexed as to why it isn't working today.
I've tested this on two systems (Linux & Mac) with the same results.
Observe:
$ cat xxx.c
#include <stdio.h>
#include <stdarg.h>
void myfoofun(const char *fmt, ...) {
va_list vl;
va_start(vl,fmt);
printf(fmt,vl);
va_end(vl);
}
int main(void) {
myfoofun("This is %s a test\n","not");
printf("This is %s a test\n","not");
return 0;
}
$ rm -f xxx;gcc -W -Wall -Werror xxx.c -o xxx && ./xxx
This is a test
This is not a test
$ ./xxx|od -bc
0000000 124 150 151 163 040 151 163 040 010 040 141 040 164 145 163 164
T h i s i s \b a t e s t
0000020 012 124 150 151 163 040 151 163 040 156 157 164 040 141 040 164
\n T h i s i s n o t a t
0000040 145 163 164 012
e s t \n
0000044
$
Where's that \b coming from???
--
(The Republican mind, in a nutshell)
You believe things that are incomprehensible, inconsistent, impossible
because we have commanded you to believe them; go then and do what is
unjust because we command it. Such people show admirable reasoning. Truly,
whoever is able to make you absurd is able to make you unjust. If the
God-given understanding of your mind does not resist a demand to believe
what is impossible, then you will not resist a demand to do wrong to that
God-given sense of justice in your heart. As soon as one faculty of your
soul has been dominated, other faculties will follow as well. And from this
derives all those crimes of religion which have overrun the world.
(Alternative condensed translation)
"Those who can make you believe absurdities, can make you commit atrocities".
[toc] | [next] | [standalone]
| From | Andrew Cooper <amc96@cam.ac.uk> |
|---|---|
| Date | 2015-04-10 22:36 +0100 |
| Message-ID | <mg9fod$top$1@flame.srcf.net> |
| In reply to | #59888 |
On 10/04/2015 21:54, Kenny McCormack wrote:
> Subtitle: Yes, Kenny posts something substantive...
>
> I'm getting a strange result with va_list & friends. I've used this stuff
> in the past, so I'm really perplexed as to why it isn't working today.
>
> I've tested this on two systems (Linux & Mac) with the same results.
>
> Observe:
>
> $ cat xxx.c
> #include <stdio.h>
> #include <stdarg.h>
>
> void myfoofun(const char *fmt, ...) {
> va_list vl;
>
> va_start(vl,fmt);
> printf(fmt,vl);
vl is a va_list, not a string, which is what printf() is going to
attempt to interpret it as, given the %s.
What you are looking to use here is vprintf().
> va_end(vl);
> }
>
> int main(void) {
> myfoofun("This is %s a test\n","not");
> printf("This is %s a test\n","not");
> return 0;
> }
>
> $ rm -f xxx;gcc -W -Wall -Werror xxx.c -o xxx && ./xxx
> This is a test
> This is not a test
> $ ./xxx|od -bc
> 0000000 124 150 151 163 040 151 163 040 010 040 141 040 164 145 163 164
> T h i s i s \b a t e s t
> 0000020 012 124 150 151 163 040 151 163 040 156 157 164 040 141 040 164
> \n T h i s i s n o t a t
> 0000040 145 163 164 012
> e s t \n
> 0000044
> $
>
> Where's that \b coming from???
Undefined behaviour.
In this case, specifically the fact that GCC (for whatever reason -
count of unused %xmm arguments by the looks of it) puts 0x00000008 in
the first element of vl.
When interpreted as as string, this is "\b".
It is somewhat curious that -Wformat, even when explicitly annotating
myfoofun() with __attribute__((format(printf, 1, 2))), doesn't manage to
catch this misuse.
~Andrew
[toc] | [prev] | [next] | [standalone]
| From | Martin Shobe <martin.shobe@yahoo.com> |
|---|---|
| Date | 2015-04-10 16:47 -0500 |
| Message-ID | <mg9gbp$gmg$1@dont-email.me> |
| In reply to | #59888 |
On 4/10/2015 3:54 PM, Kenny McCormack wrote:
> Subtitle: Yes, Kenny posts something substantive...
>
> I'm getting a strange result with va_list & friends. I've used this stuff
> in the past, so I'm really perplexed as to why it isn't working today.
>
> I've tested this on two systems (Linux & Mac) with the same results.
>
> Observe:
>
> $ cat xxx.c
> #include <stdio.h>
> #include <stdarg.h>
>
> void myfoofun(const char *fmt, ...) {
> va_list vl;
>
> va_start(vl,fmt);
> printf(fmt,vl);
> va_end(vl);
> }
Use vprintf instead of printf.
> int main(void) {
> myfoofun("This is %s a test\n","not");
> printf("This is %s a test\n","not");
> return 0;
> }
>
> $ rm -f xxx;gcc -W -Wall -Werror xxx.c -o xxx && ./xxx
> This is a test
> This is not a test
> $ ./xxx|od -bc
> 0000000 124 150 151 163 040 151 163 040 010 040 141 040 164 145 163 164
> T h i s i s \b a t e s t
> 0000020 012 124 150 151 163 040 151 163 040 156 157 164 040 141 040 164
> \n T h i s i s n o t a t
> 0000040 145 163 164 012
> e s t \n
> 0000044
> $
>
> Where's that \b coming from???
The undefined behavior caused by calling the wrong function.
Martin Shobe
[toc] | [prev] | [next] | [standalone]
| From | Robert Wessel <robertwessel2@yahoo.com> |
|---|---|
| Date | 2015-04-10 16:50 -0500 |
| Message-ID | <j9hgia9deirme5hajnn4aootsnqo746hnr@4ax.com> |
| In reply to | #59888 |
On Fri, 10 Apr 2015 20:54:44 +0000 (UTC), gazelle@shell.xmission.com
(Kenny McCormack) wrote:
>Subtitle: Yes, Kenny posts something substantive...
>
>I'm getting a strange result with va_list & friends. I've used this stuff
>in the past, so I'm really perplexed as to why it isn't working today.
>
>I've tested this on two systems (Linux & Mac) with the same results.
>
>Observe:
>
> $ cat xxx.c
>#include <stdio.h>
>#include <stdarg.h>
>
>void myfoofun(const char *fmt, ...) {
> va_list vl;
>
> va_start(vl,fmt);
> printf(fmt,vl);
> va_end(vl);
>}
>
>int main(void) {
> myfoofun("This is %s a test\n","not");
> printf("This is %s a test\n","not");
> return 0;
>}
>
> $ rm -f xxx;gcc -W -Wall -Werror xxx.c -o xxx && ./xxx
>This is a test
>This is not a test
> $ ./xxx|od -bc
>0000000 124 150 151 163 040 151 163 040 010 040 141 040 164 145 163 164
> T h i s i s \b a t e s t
>0000020 012 124 150 151 163 040 151 163 040 156 157 164 040 141 040 164
> \n T h i s i s n o t a t
>0000040 145 163 164 012
> e s t \n
>0000044
> $
>
>Where's that \b coming from???
You can't pass a va_list to printf(). Actually you can, but it's
going to try (mis)interpreting it as a string. You need to use
vprintf(), which explicitly expects a va_list as the second parameter.
[toc] | [prev] | [next] | [standalone]
| From | Malcolm McLean <malcolm.mclean5@btinternet.com> |
|---|---|
| Date | 2015-04-10 15:33 -0700 |
| Message-ID | <3b740d70-0800-4b74-8957-7ba3deb59ef9@googlegroups.com> |
| In reply to | #59892 |
On Friday, April 10, 2015 at 10:50:44 PM UTC+1, robert...@yahoo.com wrote: > > You can't pass a va_list to printf(). Actually you can, but it's > going to try (mis)interpreting it as a string. You need to use > vprintf(), which explicitly expects a va_list as the second parameter. > Yes, one of the few thing s C doesn't allow you to do is to build a va_list at runtime. Surprising, as it's pretty trivial in most assemblers - you just push the variables onto the stack or set them to the call registers.
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2015-04-10 23:02 +0100 |
| Message-ID | <87a8yf1w24.fsf@bsb.me.uk> |
| In reply to | #59888 |
gazelle@shell.xmission.com (Kenny McCormack) writes:
<snip>
> Observe:
>
> $ cat xxx.c
> #include <stdio.h>
> #include <stdarg.h>
>
> void myfoofun(const char *fmt, ...) {
> va_list vl;
>
> va_start(vl,fmt);
> printf(fmt,vl);
You need vprintf here.
> va_end(vl);
> }
>
> int main(void) {
> myfoofun("This is %s a test\n","not");
> printf("This is %s a test\n","not");
> return 0;
> }
>
> $ rm -f xxx;gcc -W -Wall -Werror xxx.c -o xxx && ./xxx
> This is a test
> This is not a test
> $ ./xxx|od -bc
> 0000000 124 150 151 163 040 151 163 040 010 040 141 040 164 145 163 164
> T h i s i s \b a t e s t
> 0000020 012 124 150 151 163 040 151 163 040 156 157 164 040 141 040 164
> \n T h i s i s n o t a t
> 0000040 145 163 164 012
> e s t \n
> 0000044
> $
>
> Where's that \b coming from???
A %s conversion specifier expects the corresponding argument to be a
pointer to the start of an array of character type and it's possible
that a va_list is indeed such a thing (or converts to such a thing in a
variadic argument position). In that case the \b comes from what
happens to be in the va_list object. But more likely its plain old
undefined behaviour from having he wrong type of argument for a
conversion specifier.
--
Ben.
[toc] | [prev] | [next] | [standalone]
| From | Jorgen Grahn <grahn+nntp@snipabacken.se> |
|---|---|
| Date | 2015-04-11 03:00 +0000 |
| Message-ID | <slrnmih3j9.2ot.grahn+nntp@frailea.sa.invalid> |
| In reply to | #59893 |
On Fri, 2015-04-10, Ben Bacarisse wrote:
> gazelle@shell.xmission.com (Kenny McCormack) writes:
> <snip>
>> Observe:
>>
>> $ cat xxx.c
>> #include <stdio.h>
>> #include <stdarg.h>
>>
>> void myfoofun(const char *fmt, ...) {
>> va_list vl;
>>
>> va_start(vl,fmt);
>> printf(fmt,vl);
>
> You need vprintf here.
>
>> va_end(vl);
>> }
>>
>> int main(void) {
>> myfoofun("This is %s a test\n","not");
>> printf("This is %s a test\n","not");
>> return 0;
>> }
>>
>> $ rm -f xxx;gcc -W -Wall -Werror xxx.c -o xxx && ./xxx
>> This is a test
>> This is not a test
>> $ ./xxx|od -bc
>> 0000000 124 150 151 163 040 151 163 040 010 040 141 040 164 145 163 164
>> T h i s i s \b a t e s t
>> 0000020 012 124 150 151 163 040 151 163 040 156 157 164 040 141 040 164
>> \n T h i s i s n o t a t
>> 0000040 145 163 164 012
>> e s t \n
>> 0000044
>> $
>>
>> Where's that \b coming from???
>
> A %s conversion specifier expects the corresponding argument to be a
> pointer to the start of an array of character type and it's possible
> that a va_list is indeed such a thing (or converts to such a thing in a
> variadic argument position). In that case the \b comes from what
> happens to be in the va_list object.
> But more likely its plain old
> undefined behaviour from having he wrong type of argument for a
> conversion specifier.
There must be something like the former going on, because gcc doesn't
warn for that printf() call, even when I add -pedantic and -std=c99.
Surprising, and tricky.
/Jorgen
--
// Jorgen Grahn <grahn@ Oo o. . .
\X/ snipabacken.se> O o .
[toc] | [prev] | [next] | [standalone]
| From | gazelle@shell.xmission.com (Kenny McCormack) |
|---|---|
| Date | 2015-04-11 03:18 +0000 |
| Message-ID | <mga3qo$9vc$1@news.xmission.com> |
| In reply to | #59897 |
In article <slrnmih3j9.2ot.grahn+nntp@frailea.sa.invalid>, Jorgen Grahn <grahn+nntp@snipabacken.se> wrote: ... >There must be something like the former going on, because gcc doesn't >warn for that printf() call, even when I add -pedantic and -std=c99. >Surprising, and tricky. Yes, as it happens, it was just a typo in the original. So, original problem solved. But, as you say, the interesting thing is that gcc didn't warn about it. One comes to rely on that - on the compiler telling you when you make an obvious typo like this. I suppose the "standards answer" is that in a variadic function, it is not guaranteed that the non-fixed arguments will get the usual arg type checking treatment. -- To most Christians, the Bible is like a software license. Nobody actually reads it. They just scroll to the bottom and click "I agree." - author unknown -
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <Richard@Damon-Family.org> |
|---|---|
| Date | 2015-04-11 00:04 -0400 |
| Message-ID | <Z21Ww.254434$Xj5.75604@fx26.iad> |
| In reply to | #59898 |
On 4/10/15 11:18 PM, Kenny McCormack wrote: > In article <slrnmih3j9.2ot.grahn+nntp@frailea.sa.invalid>, > Jorgen Grahn <grahn+nntp@snipabacken.se> wrote: > ... >> There must be something like the former going on, because gcc doesn't >> warn for that printf() call, even when I add -pedantic and -std=c99. >> Surprising, and tricky. > > Yes, as it happens, it was just a typo in the original. > So, original problem solved. > > But, as you say, the interesting thing is that gcc didn't warn about it. > One comes to rely on that - on the compiler telling you when you make an > obvious typo like this. > > I suppose the "standards answer" is that in a variadic function, it is not > guaranteed that the non-fixed arguments will get the usual arg type > checking treatment. > gcc does good checking if it can see the format string, having it would have likely gotten a warning. Without the format string, it looks like it doesn't check that you are passing something which doesn't match any format (or maybe there is a format that var_list happens to be compatible with as used in gcc).
[toc] | [prev] | [next] | [standalone]
| From | Jorgen Grahn <grahn+nntp@snipabacken.se> |
|---|---|
| Date | 2015-04-11 16:02 +0000 |
| Message-ID | <slrnmiihcq.2ot.grahn+nntp@frailea.sa.invalid> |
| In reply to | #59900 |
On Sat, 2015-04-11, Richard Damon wrote: > On 4/10/15 11:18 PM, Kenny McCormack wrote: >> In article <slrnmih3j9.2ot.grahn+nntp@frailea.sa.invalid>, >> Jorgen Grahn <grahn+nntp@snipabacken.se> wrote: >> ... >>> There must be something like the former going on, because gcc doesn't >>> warn for that printf() call, even when I add -pedantic and -std=c99. >>> Surprising, and tricky. >> >> Yes, as it happens, it was just a typo in the original. >> So, original problem solved. >> >> But, as you say, the interesting thing is that gcc didn't warn about it. >> One comes to rely on that - on the compiler telling you when you make an >> obvious typo like this. >> >> I suppose the "standards answer" is that in a variadic function, it is not >> guaranteed that the non-fixed arguments will get the usual arg type >> checking treatment. >> > > gcc does good checking if it can see the format string Wow, when I wrote the above I missed the fact that the format string was variable. I blame fever, a headache and lack of sleep. /Jorgen -- // Jorgen Grahn <grahn@ Oo o. . . \X/ snipabacken.se> O o .
[toc] | [prev] | [next] | [standalone]
| From | Ian Collins <ian-news@hotmail.com> |
|---|---|
| Date | 2015-04-12 08:27 +1200 |
| Message-ID | <cotee4FichaU1@mid.individual.net> |
| In reply to | #59900 |
Richard Damon wrote:
> On 4/10/15 11:18 PM, Kenny McCormack wrote:
>> In article <slrnmih3j9.2ot.grahn+nntp@frailea.sa.invalid>,
>> Jorgen Grahn <grahn+nntp@snipabacken.se> wrote:
>> ...
>>> There must be something like the former going on, because gcc doesn't
>>> warn for that printf() call, even when I add -pedantic and -std=c99.
>>> Surprising, and tricky.
>>
>> Yes, as it happens, it was just a typo in the original.
>> So, original problem solved.
>>
>> But, as you say, the interesting thing is that gcc didn't warn about it.
>> One comes to rely on that - on the compiler telling you when you make an
>> obvious typo like this.
>>
>> I suppose the "standards answer" is that in a variadic function, it is not
>> guaranteed that the non-fixed arguments will get the usual arg type
>> checking treatment.
>>
>
> gcc does good checking if it can see the format string, having it would
> have likely gotten a warning. Without the format string, it looks like
> it doesn't check that you are passing something which doesn't match any
> format (or maybe there is a format that var_list happens to be
> compatible with as used in gcc).
Even with the format string, gcc doesn't spot this case. Change the
printf to:
printf("%s",vl);
> /opt/gcc4.9/bin/gcc -std=c99 -Wall -pedantic xxx.c
>
Unlike
printf("%s",42);
> /opt/gcc4.9/bin/gcc -std=c99 -Wall -pedantic xxx.c
xxx.c: In function 'myfoofun':
xxx.c:8:5: warning: format '%s' expects argument of type 'char *', but
argument 2 has type 'int' [-Wformat=]
printf("%s",42);
^
--
Ian Collins
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <Richard@Damon-Family.org> |
|---|---|
| Date | 2015-04-11 17:48 -0400 |
| Message-ID | <sEgWw.349681$f5.86231@fx05.iad> |
| In reply to | #59916 |
On 4/11/15 4:27 PM, Ian Collins wrote:
> Richard Damon wrote:
>>
>> gcc does good checking if it can see the format string, having it would
>> have likely gotten a warning. Without the format string, it looks like
>> it doesn't check that you are passing something which doesn't match any
>> format (or maybe there is a format that var_list happens to be
>> compatible with as used in gcc).
>
> Even with the format string, gcc doesn't spot this case. Change the
> printf to:
>
> printf("%s",vl);
>
> > /opt/gcc4.9/bin/gcc -std=c99 -Wall -pedantic xxx.c
> >
>
> Unlike
>
> printf("%s",42);
>
> > /opt/gcc4.9/bin/gcc -std=c99 -Wall -pedantic xxx.c
> xxx.c: In function 'myfoofun':
> xxx.c:8:5: warning: format '%s' expects argument of type 'char *', but
> argument 2 has type 'int' [-Wformat=]
> printf("%s",42);
> ^
>
This might mean that gcc defines VA_LIST as some variant of char*, which
can make some sense, by definition it is safe to convert any pointer to
a char* and a char* to any other point if the pointer does point to that
type of object, and you can increment (or decrement depending on the
architecture) the pointer by the stack size of the object to get to the
next parameter on the stack. Only char* and void* have this property (on
a word addressed machine these may be bigger than other pointers), and
void* would be way too permissive in conversions.
The alternative would require an implementation namespace type for a
VA_LIST that the header maps to the standard define VA_LIST (since if
you don't include the header, that name would be in user namespace since
it isn't a keyword).
[toc] | [prev] | [next] | [standalone]
| From | Robert Wessel <robertwessel2@yahoo.com> |
|---|---|
| Date | 2015-04-12 01:06 -0500 |
| Message-ID | <6j2kia589lagtgat29souq6khqp3c9g053@4ax.com> |
| In reply to | #59916 |
On Sun, 12 Apr 2015 08:27:48 +1200, Ian Collins <ian-news@hotmail.com>
wrote:
>Richard Damon wrote:
>> On 4/10/15 11:18 PM, Kenny McCormack wrote:
>>> In article <slrnmih3j9.2ot.grahn+nntp@frailea.sa.invalid>,
>>> Jorgen Grahn <grahn+nntp@snipabacken.se> wrote:
>>> ...
>>>> There must be something like the former going on, because gcc doesn't
>>>> warn for that printf() call, even when I add -pedantic and -std=c99.
>>>> Surprising, and tricky.
>>>
>>> Yes, as it happens, it was just a typo in the original.
>>> So, original problem solved.
>>>
>>> But, as you say, the interesting thing is that gcc didn't warn about it.
>>> One comes to rely on that - on the compiler telling you when you make an
>>> obvious typo like this.
>>>
>>> I suppose the "standards answer" is that in a variadic function, it is not
>>> guaranteed that the non-fixed arguments will get the usual arg type
>>> checking treatment.
>>>
>>
>> gcc does good checking if it can see the format string, having it would
>> have likely gotten a warning. Without the format string, it looks like
>> it doesn't check that you are passing something which doesn't match any
>> format (or maybe there is a format that var_list happens to be
>> compatible with as used in gcc).
>
>Even with the format string, gcc doesn't spot this case. Change the
>printf to:
>
> printf("%s",vl);
>
> > /opt/gcc4.9/bin/gcc -std=c99 -Wall -pedantic xxx.c
> >
>
>Unlike
>
> printf("%s",42);
>
> > /opt/gcc4.9/bin/gcc -std=c99 -Wall -pedantic xxx.c
>xxx.c: In function 'myfoofun':
>xxx.c:8:5: warning: format '%s' expects argument of type 'char *', but
>argument 2 has type 'int' [-Wformat=]
> printf("%s",42);
> ^
MSVC defines a va_list as a char *, I suspect glibc is similar. It
would probably be better to define it as something like a struct or a
pointer to a struct, and then add a few extra casts to the va_*
macros.
[toc] | [prev] | [next] | [standalone]
| From | Martin Shobe <martin.shobe@yahoo.com> |
|---|---|
| Date | 2015-04-11 10:49 -0500 |
| Message-ID | <mgbfnu$jnh$1@dont-email.me> |
| In reply to | #59898 |
On 4/10/2015 10:18 PM, Kenny McCormack wrote: > In article <slrnmih3j9.2ot.grahn+nntp@frailea.sa.invalid>, > Jorgen Grahn <grahn+nntp@snipabacken.se> wrote: > ... >> There must be something like the former going on, because gcc doesn't >> warn for that printf() call, even when I add -pedantic and -std=c99. >> Surprising, and tricky. > > Yes, as it happens, it was just a typo in the original. > So, original problem solved. > > But, as you say, the interesting thing is that gcc didn't warn about it. > One comes to rely on that - on the compiler telling you when you make an > obvious typo like this. > > I suppose the "standards answer" is that in a variadic function, it is not > guaranteed that the non-fixed arguments will get the usual arg type > checking treatment. Yes, but I would still consider it a bug in their type checking. You can't catch every type error for a printf style function as doing so would allow one to also solve the halting problem, but it fails to catch it even with a constant format string and it has everything it needs to know that there's a problem there. Martin Shobe
[toc] | [prev] | [next] | [standalone]
| From | Lőrinczy Zsigmond <nospam@for.me> |
|---|---|
| Date | 2015-04-12 17:58 +0200 |
| Message-ID | <mge4n6$skf$1@speranza.aioe.org> |
| In reply to | #59888 |
To put it simply: never compile without these flags: -W -Wall -Wextra -Werror
[toc] | [prev] | [next] | [standalone]
| From | Jorgen Grahn <grahn+nntp@snipabacken.se> |
|---|---|
| Date | 2015-04-13 17:31 +0000 |
| Message-ID | <slrnminvb3.2ot.grahn+nntp@frailea.sa.invalid> |
| In reply to | #59933 |
On Sun, 2015-04-12, L??rinczy Zsigmond wrote: > To put it simply: never compile without these flags: > -W -Wall -Wextra -Werror I agree, but nitpicking: 1) He did, and for once it didn't help. 2) -W is an alias for -Wextra. 3) You're missing -std=c99 and -pedantic. (Some people think -pedantic is too much, but OTOH others think -Werror is harmful). /Jorgen -- // Jorgen Grahn <grahn@ Oo o. . . \X/ snipabacken.se> O o .
[toc] | [prev] | [next] | [standalone]
| From | gazelle@shell.xmission.com (Kenny McCormack) |
|---|---|
| Date | 2015-04-13 17:48 +0000 |
| Message-ID | <mggvhl$e6m$1@news.xmission.com> |
| In reply to | #59971 |
In article <slrnminvb3.2ot.grahn+nntp@frailea.sa.invalid>, Jorgen Grahn <grahn+nntp@snipabacken.se> wrote: >On Sun, 2015-04-12, L??rinczy Zsigmond wrote: >> To put it simply: never compile without these flags: >> -W -Wall -Wextra -Werror > >I agree, but nitpicking: > >1) He did, and for once it didn't help. Quite so. >2) -W is an alias for -Wextra. Actually, I didn't use -Wextra, but I always use -W. I didn't know (until now) that they mean the same thing. >3) You're missing -std=c99 and -pedantic. (Some people think -pedantic > is too much, but OTOH others think -Werror is harmful). I freely use gcc extensions, so things like -pedantic and so on are a non-starter for me. -- "They shall be attended by boys graced with eternal youth, who to the beholder?s eyes will seem like sprinkled pearls. When you gaze upon that scene, you will behold a kingdom blissful and glorious." --- Qur'an 76:19 ---
[toc] | [prev] | [next] | [standalone]
| From | Jorgen Grahn <grahn+nntp@snipabacken.se> |
|---|---|
| Date | 2015-04-14 20:26 +0000 |
| Message-ID | <slrnmiqu0h.2ot.grahn+nntp@frailea.sa.invalid> |
| In reply to | #59972 |
On Mon, 2015-04-13, Kenny McCormack wrote: > In article <slrnminvb3.2ot.grahn+nntp@frailea.sa.invalid>, > Jorgen Grahn <grahn+nntp@snipabacken.se> wrote: [gcc] >>2) -W is an alias for -Wextra. > > Actually, I didn't use -Wextra, but I always use -W. > I didn't know (until now) that they mean the same thing. The name change happened a couple of years ago. Or, I /noticed/ it a couple of years ago. /Jorgen -- // Jorgen Grahn <grahn@ Oo o. . . \X/ snipabacken.se> O o .
[toc] | [prev] | [next] | [standalone]
| From | Noob <root@127.0.0.1> |
|---|---|
| Date | 2015-04-14 22:58 +0200 |
| Message-ID | <mgjuv7$l6l$1@dont-email.me> |
| In reply to | #60057 |
Jorgen Grahn wrote: > Kenny McCormack wrote: > >> Actually, I didn't use -Wextra, but I always use -W. >> I didn't know (until now) that they mean the same thing. Sometimes it does pay to RTFM, dear Kenny. > The name change happened a couple of years ago. > Or, I /noticed/ it a couple of years ago. A "couple" of years ago? https://raw.githubusercontent.com/gcc-mirror/gcc/master/gcc/ChangeLog-2003 2003-01-24 o Rename -W to -Wextra.
[toc] | [prev] | [next] | [standalone]
| From | Philipp Klaus Krause <pkk@spth.de> |
|---|---|
| Date | 2015-04-16 13:08 +0200 |
| Message-ID | <mgo56u$sgb$1@solani.org> |
| In reply to | #59933 |
On 12.04.2015 17:58, Lőrinczy Zsigmond wrote: > To put it simply: never compile without these flags: > -W -Wall -Wextra -Werror I'd rather say the opposite: Never compile with -Werror. And more important: never ship anything (be it tarball, snapshots, or something in your public repository) that uses -Werror in the build system. And I really can't see any advantage that -Werror would provide. On the other hand, there are lots of disadvantages: You write perfectly fine code today, and ship it. Tomorrow, a compiler vendor decides they don't like the coding style you used, and emit a warning on it. Now with -Werror compilation will fail for whoever wants to compile your code with the latest compiler version. I've seent his happen in GNU binutils, where it is hard o get out the -Werror, and where there was a time when the latest released binutils failed to compile with the latest released GCC due to -Werror turning a "Warning: right-hand operand of comma expression has no effect" into an error. Philipp
[toc] | [prev] | [next] | [standalone]
Page 1 of 11 [1] 2 3 … 11 Next page →
Back to top | Article view | comp.lang.c
csiph-web