Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #71186 > unrolled thread
| Started by | "Morten W. Petersen" <morphex@gmail.com> |
|---|---|
| First post | 2015-09-25 04:02 +0200 |
| Last post | 2015-10-02 00:16 +0200 |
| Articles | 20 on this page of 332 — 34 participants |
Back to article view | Back to comp.lang.c
Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-25 04:02 +0200
Re: Unexpected and difficult to understand SIGSEGV "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-09-24 19:51 -0700
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-25 14:09 +0200
Re: Unexpected and difficult to understand SIGSEGV John Gordon <gordon@panix.com> - 2015-09-25 04:32 +0000
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-25 14:09 +0200
Re: Unexpected and difficult to understand SIGSEGV Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-09-25 22:07 +0000
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-09-25 18:46 -0400
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-09-26 10:57 +1200
Re: Unexpected and difficult to understand SIGSEGV Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-09-25 21:40 -0700
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-09-26 16:51 +1200
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-09-26 10:45 +0100
Re: Unexpected and difficult to understand SIGSEGV Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-09-26 03:39 -0700
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-09-26 12:20 +0100
Re: Unexpected and difficult to understand SIGSEGV Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-09-26 06:39 -0700
Re: Unexpected and difficult to understand SIGSEGV fir <profesor.fir@gmail.com> - 2015-09-27 01:45 -0700
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-26 23:11 +0200
Re: Unexpected and difficult to understand SIGSEGV jacobnavia <jacob@jacob.remcomp.fr> - 2015-09-25 10:28 +0200
Re: Unexpected and difficult to understand SIGSEGV Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-09-25 10:33 +0000
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-25 14:05 +0200
Re: Unexpected and difficult to understand SIGSEGV Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-09-25 16:44 +0000
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-25 14:08 +0200
Re: Unexpected and difficult to understand SIGSEGV Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-09-25 10:55 +0100
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-25 14:00 +0200
Re: Unexpected and difficult to understand SIGSEGV luser droog <luser.droog@gmail.com> - 2015-09-25 09:40 -0700
Re: Unexpected and difficult to understand SIGSEGV Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-09-25 20:25 +0100
Re: Unexpected and difficult to understand SIGSEGV <william@wilbur.25thandClement.com> - 2015-09-25 19:07 -0700
Re: Unexpected and difficult to understand SIGSEGV Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-09-26 10:47 +0100
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-09-26 10:34 -0400
Re: Unexpected and difficult to understand SIGSEGV Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-09-26 15:28 +0000
Re: Unexpected and difficult to understand SIGSEGV Tim Rentsch <txr@alumni.caltech.edu> - 2015-09-26 17:32 -0700
Re: Unexpected and difficult to understand SIGSEGV Noob <root@127.0.0.1> - 2015-09-27 09:59 +0200
Re: Unexpected and difficult to understand SIGSEGV Tim Rentsch <txr@alumni.caltech.edu> - 2015-09-30 02:52 -0700
Re: Unexpected and difficult to understand SIGSEGV Noob <root@127.0.0.1> - 2015-09-30 20:13 +0200
Re: Unexpected and difficult to understand SIGSEGV Tim Rentsch <txr@alumni.caltech.edu> - 2015-10-04 16:00 -0700
Re: Unexpected and difficult to understand SIGSEGV Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-09-28 08:17 +0000
Re: Unexpected and difficult to understand SIGSEGV Tim Rentsch <txr@alumni.caltech.edu> - 2015-09-30 04:00 -0700
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-10-01 09:34 +1300
Re: Unexpected and difficult to understand SIGSEGV Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-10-01 19:05 +0000
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-10-02 08:25 +1300
Re: Unexpected and difficult to understand SIGSEGV Tim Rentsch <txr@alumni.caltech.edu> - 2015-10-04 16:02 -0700
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-10-05 12:57 +1300
Re: Unexpected and difficult to understand SIGSEGV Tim Rentsch <txr@alumni.caltech.edu> - 2015-10-06 09:23 -0700
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-10-07 11:18 +1300
Re: Unexpected and difficult to understand SIGSEGV Tim Rentsch <txr@alumni.caltech.edu> - 2015-10-09 13:52 -0700
Re: Unexpected and difficult to understand SIGSEGV David Brown <david.brown@hesbynett.no> - 2015-09-29 09:51 +0200
Re: Unexpected and difficult to understand SIGSEGV Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-09-29 11:07 +0000
Re: Unexpected and difficult to understand SIGSEGV David Brown <david.brown@hesbynett.no> - 2015-09-29 15:09 +0200
Re: Unexpected and difficult to understand SIGSEGV Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-09-30 07:34 +0000
Re: Unexpected and difficult to understand SIGSEGV David Brown <david.brown@hesbynett.no> - 2015-09-30 10:33 +0200
Re: Unexpected and difficult to understand SIGSEGV Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-09-30 11:14 +0100
Re: Unexpected and difficult to understand SIGSEGV David Brown <david.brown@hesbynett.no> - 2015-09-30 12:26 +0200
Re: Unexpected and difficult to understand SIGSEGV Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-09-30 11:58 +0100
Re: Unexpected and difficult to understand SIGSEGV Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-10-01 19:16 +0000
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-30 16:21 +0200
Re: Unexpected and difficult to understand SIGSEGV Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-10-01 19:27 +0000
Re: Unexpected and difficult to understand SIGSEGV Tim Rentsch <txr@alumni.caltech.edu> - 2015-10-01 07:58 -0700
Re: Unexpected and difficult to understand SIGSEGV David Brown <david.brown@hesbynett.no> - 2015-10-01 21:52 +0200
Re: Unexpected and difficult to understand SIGSEGV Tim Rentsch <txr@alumni.caltech.edu> - 2015-10-04 16:10 -0700
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-09-27 11:15 +0100
Re: Unexpected and difficult to understand SIGSEGV Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-09-28 08:47 +0000
Re: Unexpected and difficult to understand SIGSEGV Andrew Cooper <amc96@cam.ac.uk> - 2015-09-26 00:02 +0100
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-27 00:02 +0200
Re: Unexpected and difficult to understand SIGSEGV Geoff <geoff@invalid.invalid> - 2015-09-26 23:32 -0700
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-27 22:10 +0200
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-09-27 17:01 -0400
Re: Unexpected and difficult to understand SIGSEGV Richard Heathfield <rjh@cpax.org.uk> - 2015-09-27 22:15 +0100
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-27 23:36 +0200
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-27 23:33 +0200
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-09-28 10:40 +1300
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-27 23:58 +0200
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-09-28 11:08 +1300
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-28 00:25 +0200
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-09-28 12:50 +1300
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-28 02:06 +0200
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-09-28 13:15 +1300
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-28 02:20 +0200
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-09-28 13:24 +1300
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-28 02:44 +0200
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-09-28 13:50 +1300
Re: Unexpected and difficult to understand SIGSEGV Philip Lantz <prl@canterey.us> - 2015-09-27 23:44 -0700
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-09-28 20:17 +1300
Re: Unexpected and difficult to understand SIGSEGV Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-09-28 01:06 -0700
Re: Unexpected and difficult to understand SIGSEGV David Brown <david.brown@hesbynett.no> - 2015-09-28 16:59 +0200
Re: Unexpected and difficult to understand SIGSEGV Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-09-28 09:23 -0700
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-09-29 07:47 +1300
Re: Unexpected and difficult to understand SIGSEGV David Brown <david.brown@hesbynett.no> - 2015-09-28 13:46 +0200
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-09-29 07:52 +1300
Re: Unexpected and difficult to understand SIGSEGV David Brown <david.brown@hesbynett.no> - 2015-09-29 10:15 +0200
Re: Unexpected and difficult to understand SIGSEGV raltbos@xs4all.nl (Richard Bos) - 2015-10-02 09:55 +0000
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-10-02 11:59 -0400
Re: Unexpected and difficult to understand SIGSEGV Philip Lantz <prl@canterey.us> - 2015-10-03 11:51 -0700
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-10-03 15:25 -0400
Re: Unexpected and difficult to understand SIGSEGV Tim Rentsch <txr@alumni.caltech.edu> - 2015-10-04 14:50 -0700
Re: Unexpected and difficult to understand SIGSEGV Richard Damon <Richard@Damon-Family.org> - 2015-09-27 18:32 -0400
Re: Unexpected and difficult to understand SIGSEGV asetofsymbols@gmail.com - 2015-09-27 17:37 -0700
Re: Unexpected and difficult to understand SIGSEGV Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-09-27 17:50 -0700
Re: Unexpected and difficult to understand SIGSEGV Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-09-28 18:18 +0000
Re: Unexpected and difficult to understand SIGSEGV Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-09-28 11:31 -0700
Re: Unexpected and difficult to understand SIGSEGV Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-09-29 07:37 +0000
Re: Unexpected and difficult to understand SIGSEGV asetofsymbols@gmail.com - 2015-09-27 17:38 -0700
Re: Unexpected and difficult to understand SIGSEGV asetofsymbols@gmail.com - 2015-09-27 17:39 -0700
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-09-28 13:42 +1300
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-28 02:46 +0200
Re: Unexpected and difficult to understand SIGSEGV raltbos@xs4all.nl (Richard Bos) - 2015-10-02 09:56 +0000
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-09-27 18:20 -0400
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-09-27 15:54 -0700
Re: Unexpected and difficult to understand SIGSEGV Eric Sosman <esosman@comcast-dot-net.invalid> - 2015-09-27 18:23 -0400
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-28 00:33 +0200
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-09-28 11:42 +1300
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-28 01:04 +0200
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-09-28 12:32 +1300
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-28 01:37 +0200
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-09-27 16:53 -0700
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-09-28 00:21 +0100
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-28 01:30 +0200
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-09-28 00:41 +0100
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-28 01:52 +0200
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-09-28 12:59 +1300
Re: Unexpected and difficult to understand SIGSEGV David Brown <david.brown@hesbynett.no> - 2015-09-28 17:07 +0200
Re: Unexpected and difficult to understand SIGSEGV Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-09-30 11:17 +0000
Re: Unexpected and difficult to understand SIGSEGV supercat@casperkitty.com - 2015-09-30 06:08 -0700
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-09-27 17:09 -0700
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-28 02:17 +0200
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-09-28 09:00 -0700
Re: Unexpected and difficult to understand SIGSEGV ais523 <ais523@nethack4.org> - 2015-10-01 14:05 +0000
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-10-01 16:23 +0200
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-10-01 10:26 -0400
Re: Unexpected and difficult to understand SIGSEGV David Brown <david.brown@hesbynett.no> - 2015-10-01 16:53 +0200
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-10-01 11:26 -0400
Re: Unexpected and difficult to understand SIGSEGV David Brown <david.brown@hesbynett.no> - 2015-10-01 21:57 +0200
Re: Unexpected and difficult to understand SIGSEGV supercat@casperkitty.com - 2015-10-01 13:30 -0700
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-10-01 13:57 -0700
Re: Unexpected and difficult to understand SIGSEGV Eric Sosman <esosman@comcast-dot-net.invalid> - 2015-10-01 17:19 -0400
Re: Unexpected and difficult to understand SIGSEGV supercat@casperkitty.com - 2015-10-01 15:38 -0700
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-10-01 17:14 -0700
Re: Unexpected and difficult to understand SIGSEGV Tim Rentsch <txr@alumni.caltech.edu> - 2015-10-04 14:19 -0700
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-10-04 15:01 -0700
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-10-04 18:26 -0400
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-10-04 17:53 -0700
Re: Unexpected and difficult to understand SIGSEGV Richard Damon <Richard@Damon-Family.org> - 2015-10-04 18:37 -0400
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-10-04 19:13 -0400
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-10-04 17:57 -0700
Re: Unexpected and difficult to understand SIGSEGV Richard Damon <Richard@Damon-Family.org> - 2015-10-04 21:57 -0400
Re: Unexpected and difficult to understand SIGSEGV Tim Rentsch <txr@alumni.caltech.edu> - 2015-10-05 01:53 -0700
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-10-05 09:37 -0700
Re: Unexpected and difficult to understand SIGSEGV Tim Rentsch <txr@alumni.caltech.edu> - 2015-10-09 14:10 -0700
Re: Unexpected and difficult to understand SIGSEGV supercat@casperkitty.com - 2015-10-09 14:35 -0700
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-10-10 11:43 +1300
Re: Unexpected and difficult to understand SIGSEGV Tim Rentsch <txr@alumni.caltech.edu> - 2015-10-12 09:17 -0700
Re: Unexpected and difficult to understand SIGSEGV supercat@casperkitty.com - 2015-10-12 12:32 -0700
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-10-12 14:12 -0700
Re: Unexpected and difficult to understand SIGSEGV supercat@casperkitty.com - 2015-10-12 14:52 -0700
Re: Unexpected and difficult to understand SIGSEGV glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-10-13 03:00 +0000
Re: Unexpected and difficult to understand SIGSEGV supercat@casperkitty.com - 2015-10-12 23:34 -0700
Re: Unexpected and difficult to understand SIGSEGV raltbos@xs4all.nl (Richard Bos) - 2015-10-14 11:00 +0000
Re: Unexpected and difficult to understand SIGSEGV supercat@casperkitty.com - 2015-10-14 08:34 -0700
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-10-14 11:34 -0700
Re: Unexpected and difficult to understand SIGSEGV supercat@casperkitty.com - 2015-10-14 11:57 -0700
Re: Unexpected and difficult to understand SIGSEGV glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-10-15 00:03 +0000
Re: Unexpected and difficult to understand SIGSEGV Tim Rentsch <txr@alumni.caltech.edu> - 2015-10-15 10:57 -0700
Re: Unexpected and difficult to understand SIGSEGV raltbos@xs4all.nl (Richard Bos) - 2015-10-20 16:06 +0000
Re: Unexpected and difficult to understand SIGSEGV Tim Rentsch <txr@alumni.caltech.edu> - 2015-10-17 07:32 -0700
Re: Unexpected and difficult to understand SIGSEGV supercat@casperkitty.com - 2015-10-17 07:51 -0700
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-10-17 15:51 -0700
Re: Unexpected and difficult to understand SIGSEGV raltbos@xs4all.nl (Richard Bos) - 2015-10-02 10:09 +0000
Re: Unexpected and difficult to understand SIGSEGV Eric Sosman <esosman@comcast-dot-net.invalid> - 2015-10-02 08:55 -0400
Re: Unexpected and difficult to understand SIGSEGV supercat@casperkitty.com - 2015-10-02 08:59 -0700
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-10-02 17:35 -0700
Re: Unexpected and difficult to understand SIGSEGV supercat@casperkitty.com - 2015-10-03 10:02 -0700
Re: Unexpected and difficult to understand SIGSEGV Robert Wessel <robertwessel2@yahoo.com> - 2015-10-03 16:11 -0500
Re: Unexpected and difficult to understand SIGSEGV Eric Sosman <esosman@comcast-dot-net.invalid> - 2015-10-03 17:27 -0400
Re: Unexpected and difficult to understand SIGSEGV Robert Wessel <robertwessel2@yahoo.com> - 2015-10-03 16:58 -0500
Re: Unexpected and difficult to understand SIGSEGV supercat@casperkitty.com - 2015-10-03 15:16 -0700
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-10-03 18:21 -0400
Re: Unexpected and difficult to understand SIGSEGV Eric Sosman <esosman@comcast-dot-net.invalid> - 2015-10-03 18:23 -0400
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-10-03 18:52 -0400
Re: Unexpected and difficult to understand SIGSEGV supercat@casperkitty.com - 2015-10-03 16:16 -0700
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-10-03 19:13 -0700
Re: Unexpected and difficult to understand SIGSEGV supercat@casperkitty.com - 2015-10-03 23:34 -0700
Re: Unexpected and difficult to understand SIGSEGV glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-10-04 07:09 +0000
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-10-04 14:43 -0700
Re: Unexpected and difficult to understand SIGSEGV Robert Wessel <robertwessel2@yahoo.com> - 2015-10-04 03:19 -0500
Re: Unexpected and difficult to understand SIGSEGV Tim Rentsch <txr@alumni.caltech.edu> - 2015-10-04 14:48 -0700
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-10-04 16:26 -0700
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-10-02 13:21 -0700
Re: Unexpected and difficult to understand SIGSEGV Eric Sosman <esosman@comcast-dot-net.invalid> - 2015-10-02 17:05 -0400
Re: Unexpected and difficult to understand SIGSEGV supercat@casperkitty.com - 2015-10-02 15:11 -0700
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-10-02 20:55 -0700
Re: Unexpected and difficult to understand SIGSEGV supercat@casperkitty.com - 2015-10-03 12:00 -0700
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-10-03 16:52 -0700
Re: Unexpected and difficult to understand SIGSEGV Tim Rentsch <txr@alumni.caltech.edu> - 2015-10-04 14:40 -0700
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-10-01 22:02 -0400
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-10-02 10:09 +0100
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-10-02 08:19 -0700
Re: Unexpected and difficult to understand SIGSEGV Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-10-02 03:17 -0700
Re: Unexpected and difficult to understand SIGSEGV David Brown <david.brown@hesbynett.no> - 2015-10-02 13:02 +0200
Re: Unexpected and difficult to understand SIGSEGV Philip Lantz <prl@canterey.us> - 2015-10-01 18:33 -0700
Re: Unexpected and difficult to understand SIGSEGV Eric Sosman <esosman@comcast-dot-net.invalid> - 2015-10-01 11:17 -0400
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-10-01 17:06 +0100
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-10-01 11:45 -0700
Re: Unexpected and difficult to understand SIGSEGV raltbos@xs4all.nl (Richard Bos) - 2015-10-02 10:21 +0000
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-10-02 11:36 +0100
Re: Unexpected and difficult to understand SIGSEGV Richard Heathfield <rjh@cpax.org.uk> - 2015-10-02 11:44 +0100
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-10-02 13:24 +0100
Re: Unexpected and difficult to understand SIGSEGV Richard Heathfield <rjh@cpax.org.uk> - 2015-10-02 15:31 +0100
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-10-02 18:04 +0100
Re: Unexpected and difficult to understand SIGSEGV Richard Heathfield <rjh@cpax.org.uk> - 2015-10-02 18:21 +0100
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-10-02 21:04 +0100
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-10-03 08:29 +0200
Re: Unexpected and difficult to understand SIGSEGV David Brown <david.brown@hesbynett.no> - 2015-10-03 16:47 +0200
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-10-03 17:37 +0100
Re: Unexpected and difficult to understand SIGSEGV Richard Heathfield <rjh@cpax.org.uk> - 2015-10-03 17:54 +0100
Re: Unexpected and difficult to understand SIGSEGV David Brown <david.brown@hesbynett.no> - 2015-10-04 18:16 +0200
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-10-04 18:13 +0100
Re: Unexpected and difficult to understand SIGSEGV Richard Heathfield <rjh@cpax.org.uk> - 2015-10-04 18:22 +0100
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-10-04 20:17 +0100
Re: Unexpected and difficult to understand SIGSEGV Richard Heathfield <rjh@cpax.org.uk> - 2015-10-04 21:07 +0100
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-10-04 22:10 +0100
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-10-05 09:24 +1300
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-10-04 22:15 +0100
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-10-05 10:38 +1300
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-10-04 23:02 +0100
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-10-05 11:10 +1300
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-10-04 23:51 +0100
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-10-05 11:56 +1300
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-10-05 07:38 +1300
Re: Unexpected and difficult to understand SIGSEGV David Brown <david.brown@hesbynett.no> - 2015-10-04 23:51 +0200
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-10-04 23:44 +0100
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-10-05 11:52 +1300
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-10-05 00:09 +0100
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-10-05 13:00 +1300
Re: Unexpected and difficult to understand SIGSEGV Geoff <geoff@invalid.invalid> - 2015-10-04 17:14 -0700
Re: Unexpected and difficult to understand SIGSEGV Philip Lantz <prl@canterey.us> - 2015-10-05 09:40 -0700
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-10-05 18:32 +0100
Re: Unexpected and difficult to understand SIGSEGV Philip Lantz <prl@canterey.us> - 2015-10-05 21:59 -0700
Re: Unexpected and difficult to understand SIGSEGV Tim Rentsch <txr@alumni.caltech.edu> - 2015-10-05 01:13 -0700
Re: Unexpected and difficult to understand SIGSEGV raltbos@xs4all.nl (Richard Bos) - 2015-10-06 17:14 +0000
Re: Unexpected and difficult to understand SIGSEGV Gareth Owen <gwowen@gmail.com> - 2015-10-02 14:56 +0100
Re: Unexpected and difficult to understand SIGSEGV Richard Heathfield <rjh@cpax.org.uk> - 2015-10-02 16:31 +0100
Re: Unexpected and difficult to understand SIGSEGV Gareth Owen <gwowen@gmail.com> - 2015-10-02 20:11 +0100
Re: Unexpected and difficult to understand SIGSEGV jadill33@gmail.com - 2015-10-02 09:18 -0700
Re: Unexpected and difficult to understand SIGSEGV Gareth Owen <gwowen@gmail.com> - 2015-10-02 20:14 +0100
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-10-02 10:20 -0700
Re: Unexpected and difficult to understand SIGSEGV raltbos@xs4all.nl (Richard Bos) - 2015-10-04 14:03 +0000
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-10-01 09:28 -0700
Re: Unexpected and difficult to understand SIGSEGV Rosario19 <Ros@invalid.invalid> - 2015-10-01 18:53 +0200
Re: Unexpected and difficult to understand SIGSEGV Rosario19 <Ros@invalid.invalid> - 2015-10-02 06:26 +0200
Generating header files (Was: Unexpected and difficult to understand SIGSEGV) Roberto Waltman <usenet@rwaltman.com> - 2015-10-01 13:40 -0400
Re: Generating header files (Was: Unexpected and difficult to understand SIGSEGV) "Morten W. Petersen" <morphex@gmail.com> - 2015-10-01 23:58 +0200
Re: Unexpected and difficult to understand SIGSEGV Tim Rentsch <txr@alumni.caltech.edu> - 2015-10-04 14:06 -0700
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-09-27 21:05 -0400
Re: Unexpected and difficult to understand SIGSEGV David Brown <david.brown@hesbynett.no> - 2015-09-29 10:26 +0200
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-09-27 21:15 -0400
Re: Unexpected and difficult to understand SIGSEGV Eric Sosman <esosman@comcast-dot-net.invalid> - 2015-09-28 09:52 -0400
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-09-28 10:36 -0400
Re: Unexpected and difficult to understand SIGSEGV Eric Sosman <esosman@comcast-dot-net.invalid> - 2015-09-28 10:40 -0400
Re: Unexpected and difficult to understand SIGSEGV Richard Heathfield <rjh@cpax.org.uk> - 2015-09-28 15:55 +0100
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-29 01:16 +0200
Re: Unexpected and difficult to understand SIGSEGV Richard Heathfield <rjh@cpax.org.uk> - 2015-09-29 00:26 +0100
Re: Unexpected and difficult to understand SIGSEGV David Brown <david.brown@hesbynett.no> - 2015-09-29 10:34 +0200
Re: Unexpected and difficult to understand SIGSEGV Richard Heathfield <rjh@cpax.org.uk> - 2015-09-29 15:50 +0100
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-09-29 11:16 -0400
Re: Unexpected and difficult to understand SIGSEGV Richard Heathfield <rjh@cpax.org.uk> - 2015-09-29 16:22 +0100
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-09-29 13:15 -0400
Re: Unexpected and difficult to understand SIGSEGV Richard Heathfield <rjh@cpax.org.uk> - 2015-09-29 18:56 +0100
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-09-29 07:04 -0400
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-30 00:07 +0200
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-09-29 18:13 -0700
Re: Unexpected and difficult to understand SIGSEGV supercat@casperkitty.com - 2015-09-29 21:57 -0700
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-09-30 01:57 -0400
Re: Unexpected and difficult to understand SIGSEGV jadill33@gmail.com - 2015-09-30 06:01 -0700
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-30 16:11 +0200
Re: Unexpected and difficult to understand SIGSEGV Bartc <bc@freeuk.com> - 2015-09-30 14:12 +0100
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-30 16:15 +0200
Re: Unexpected and difficult to understand SIGSEGV Geoff <geoff@invalid.invalid> - 2015-09-30 08:40 -0700
Re: Unexpected and difficult to understand SIGSEGV Rosario19 <Ros@invalid.invalid> - 2015-09-30 22:28 +0200
Re: Unexpected and difficult to understand SIGSEGV Rosario19 <Ros@invalid.invalid> - 2015-09-30 22:31 +0200
Re: Unexpected and difficult to understand SIGSEGV Eric Sosman <esosman@comcast-dot-net.invalid> - 2015-09-30 16:53 -0400
Re: Unexpected and difficult to understand SIGSEGV Rosario19 <Ros@invalid.invalid> - 2015-09-30 23:19 +0200
Re: Unexpected and difficult to understand SIGSEGV Rosario19 <Ros@invalid.invalid> - 2015-09-30 23:32 +0200
Re: Unexpected and difficult to understand SIGSEGV Eric Sosman <esosman@comcast-dot-net.invalid> - 2015-09-30 18:17 -0400
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-10-01 03:19 +0200
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-09-30 22:01 -0400
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-10-02 00:46 +0200
Re: Unexpected and difficult to understand SIGSEGV Geoff <geoff@invalid.invalid> - 2015-09-27 17:44 -0700
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-09-28 13:51 +1300
Re: Unexpected and difficult to understand SIGSEGV Geoff <geoff@invalid.invalid> - 2015-09-27 18:04 -0700
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-28 03:39 +0200
Re: Unexpected and difficult to understand SIGSEGV James Kuyper <jameskuyper@verizon.net> - 2015-09-27 22:03 -0400
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-28 04:16 +0200
Re: Unexpected and difficult to understand SIGSEGV Ian Collins <ian-news@hotmail.com> - 2015-09-28 15:19 +1300
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-28 04:23 +0200
Re: Unexpected and difficult to understand SIGSEGV David Brown <david.brown@hesbynett.no> - 2015-09-29 14:11 +0200
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-30 00:15 +0200
Re: Unexpected and difficult to understand SIGSEGV Keith Thompson <kst-u@mib.org> - 2015-09-29 18:14 -0700
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-10-02 00:41 +0200
Re: Unexpected and difficult to understand SIGSEGV Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-09-27 19:58 -0700
Re: Unexpected and difficult to understand SIGSEGV David Brown <david.brown@hesbynett.no> - 2015-09-29 10:43 +0200
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-30 00:16 +0200
Re: Unexpected and difficult to understand SIGSEGV Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-09-29 15:51 -0700
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-30 16:37 +0200
Strings (was Re: Unexpected and difficult to understand SIGSEGV) supercat@casperkitty.com - 2015-09-30 09:12 -0700
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) Bartc <bc@freeuk.com> - 2015-09-30 17:34 +0100
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) supercat@casperkitty.com - 2015-09-30 11:29 -0700
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) Bartc <bc@freeuk.com> - 2015-09-30 20:00 +0100
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) supercat@casperkitty.com - 2015-09-30 12:49 -0700
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) Bartc <bc@freeuk.com> - 2015-09-30 22:26 +0100
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) supercat@casperkitty.com - 2015-09-30 16:27 -0700
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) Bartc <bc@freeuk.com> - 2015-10-01 09:56 +0100
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) "Morten W. Petersen" <morphex@gmail.com> - 2015-10-01 03:08 +0200
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-09-30 13:10 -0700
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) Ian Collins <ian-news@hotmail.com> - 2015-10-01 09:23 +1300
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-09-30 19:02 -0700
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) Richard Heathfield <rjh@cpax.org.uk> - 2015-10-01 03:12 +0100
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) Bartc <bc@freeuk.com> - 2015-10-01 11:15 +0100
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) Richard Heathfield <rjh@cpax.org.uk> - 2015-10-01 11:36 +0100
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-10-01 05:49 -0700
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) David Brown <david.brown@hesbynett.no> - 2015-10-01 16:41 +0200
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) Ian Collins <ian-news@hotmail.com> - 2015-10-01 15:16 +1300
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-09-30 19:10 -0700
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) Ian Collins <ian-news@hotmail.com> - 2015-10-01 15:20 +1300
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) Philip Lantz <prl@canterey.us> - 2015-10-01 01:26 -0700
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-10-01 02:16 -0700
Re: Strings (was Re: Unexpected and difficult to understand SIGSEGV) Martin Shobe <martin.shobe@yahoo.com> - 2015-10-01 08:34 -0500
Re: Unexpected and difficult to understand SIGSEGV Geoff <geoff@invalid.invalid> - 2015-09-27 19:06 -0700
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-28 04:18 +0200
Re: Unexpected and difficult to understand SIGSEGV Geoff <geoff@invalid.invalid> - 2015-09-27 21:32 -0700
Re: Unexpected and difficult to understand SIGSEGV Geoff <geoff@invalid.invalid> - 2015-09-27 07:54 -0700
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-09-27 17:16 +0200
Re: Unexpected and difficult to understand SIGSEGV Eric Sosman <esosman@comcast-dot-net.invalid> - 2015-09-27 11:21 -0400
Re: Unexpected and difficult to understand SIGSEGV Geoff <geoff@invalid.invalid> - 2015-09-27 08:59 -0700
Re: Unexpected and difficult to understand SIGSEGV "Morten W. Petersen" <morphex@gmail.com> - 2015-10-02 00:16 +0200
Page 1 of 17 [1] 2 3 … 17 Next page →
| From | "Morten W. Petersen" <morphex@gmail.com> |
|---|---|
| Date | 2015-09-25 04:02 +0200 |
| Subject | Unexpected and difficult to understand SIGSEGV |
| Message-ID | <mu29uk$iaf$1@speranza.aioe.org> |
Hi there. Once again I'm working on the Smash XML project, and I'm getting a SIGSEGV when calling a function. The line that ends up in a SIGSEGV is https://github.com/morphex/smash_xml/blob/6b558ae0347c04992d0f3c2306373a83d1c2765e/tests.c#L236 And gdb says this after "make debug; gdb ./decode_xml": (gdb) run [...] test_parse_file Program received signal SIGSEGV, Segmentation fault. __chkstk_ms () at /usr/src/debug/gcc-4.9.3-1/libgcc/config/i386/cygwin.S:172 172 orl $0x0, (%ecx) /* probe there */ (gdb) print $ecx $1 = 600600 (gdb) So somewhere between the function call and this line https://github.com/morphex/smash_xml/blob/6b558ae0347c04992d0f3c2306373a83d1c2765e/decode_xml.c#L1020 in the called function, something goes wrong and I can't quite figure out what it is. Any ideas? Regards, Morten
[toc] | [next] | [standalone]
| From | "Chris M. Thomasson" <nospam@nospam.nospam> |
|---|---|
| Date | 2015-09-24 19:51 -0700 |
| Message-ID | <mu2cs0$nfm$1@speranza.aioe.org> |
| In reply to | #71186 |
> "Morten W. Petersen" wrote in message > news:mu29uk$iaf$1@speranza.aioe.org... > Hi there. > Once again I'm working on the Smash XML project, and I'm getting a > SIGSEGV when calling a function. > The line that ends up in a SIGSEGV is > https://github.com/morphex/smash_xml/blob/6b558ae0347c04992d0f3c2306373a83d1c2765e/tests.c#L236 [...] I wonder if an output stream is in error? I just don't know. I wonder if the streams underlying write function failed? Check `fflush()' for errors? ;^o
[toc] | [prev] | [next] | [standalone]
| From | "Morten W. Petersen" <morphex@gmail.com> |
|---|---|
| Date | 2015-09-25 14:09 +0200 |
| Message-ID | <mu3di7$s5p$3@speranza.aioe.org> |
| In reply to | #71187 |
On 25.09.2015 04:51, Chris M. Thomasson wrote: > > >> "Morten W. Petersen" wrote in message >> news:mu29uk$iaf$1@speranza.aioe.org... > >> Hi there. > >> Once again I'm working on the Smash XML project, and I'm getting a >> SIGSEGV when calling a function. > >> The line that ends up in a SIGSEGV is > >> https://github.com/morphex/smash_xml/blob/6b558ae0347c04992d0f3c2306373a83d1c2765e/tests.c#L236 >> > > [...] > > I wonder if an output stream is in error? I just don't know. > > I wonder if the streams underlying write function failed? > > Check `fflush()' for errors? Well I haven't gotten errors like this before, so yes that sounds like a good idea. -Morten
[toc] | [prev] | [next] | [standalone]
| From | John Gordon <gordon@panix.com> |
|---|---|
| Date | 2015-09-25 04:32 +0000 |
| Message-ID | <mu2iov$6d2$1@reader1.panix.com> |
| In reply to | #71186 |
In <mu29uk$iaf$1@speranza.aioe.org> "Morten W. Petersen" <morphex@gmail.com> writes:
> The line that ends up in a SIGSEGV is
> https://github.com/morphex/smash_xml/blob/6b558ae0347c04992d0f3c2306373a83d1c2765e/tests.c#L236
When you get a SEGV, it's often the case that the true cause of the error
is much earlier in the program. The line of code that generates the SEGV
may be perfectly innocent.
--
John Gordon A is for Amy, who fell down the stairs
gordon@panix.com B is for Basil, assaulted by bears
-- Edward Gorey, "The Gashlycrumb Tinies"
[toc] | [prev] | [next] | [standalone]
| From | "Morten W. Petersen" <morphex@gmail.com> |
|---|---|
| Date | 2015-09-25 14:09 +0200 |
| Message-ID | <mu3dh8$s5p$2@speranza.aioe.org> |
| In reply to | #71188 |
On 25.09.2015 06:32, John Gordon wrote: > In <mu29uk$iaf$1@speranza.aioe.org> "Morten W. Petersen" <morphex@gmail.com> writes: > >> The line that ends up in a SIGSEGV is > >> https://github.com/morphex/smash_xml/blob/6b558ae0347c04992d0f3c2306373a83d1c2765e/tests.c#L236 > > When you get a SEGV, it's often the case that the true cause of the error > is much earlier in the program. The line of code that generates the SEGV > may be perfectly innocent. OK. -Morten
[toc] | [prev] | [next] | [standalone]
| From | Jorgen Grahn <grahn+nntp@snipabacken.se> |
|---|---|
| Date | 2015-09-25 22:07 +0000 |
| Message-ID | <slrnn0bhd4.eij.grahn+nntp@frailea.sa.invalid> |
| In reply to | #71188 |
On Fri, 2015-09-25, John Gordon wrote: > In <mu29uk$iaf$1@speranza.aioe.org> "Morten W. Petersen" <morphex@gmail.com> writes: > >> The line that ends up in a SIGSEGV is > >> https://github.com/morphex/smash_xml/blob/6b558ae0347c04992d0f3c2306373a83d1c2765e/tests.c#L236 > > When you get a SEGV, it's often the case that the true cause of the error > is much earlier in the program. The line of code that generates the SEGV > may be perfectly innocent. It's funny -- and maybe I'm tempting fate by writing this -- but I've done a lot of troubleshooting over the years. Rarely or never have I been in a situation where the crash or error at time T was caused by a bug at time T0, which I couldn't find. Detective work is usually needed, and you need to reproduce the problem with changes to the source code ... but it seems to me there have always been clues for me to find. What I want to say is, I guess: yes, having gdb looking at the SEGV doesn't mean you're looking at the bug ... but you should also not give up. Finding the bug in such circumstances is fun and exciting, and a valuable skill. /Jorgen -- // Jorgen Grahn <grahn@ Oo o. . . \X/ snipabacken.se> O o .
[toc] | [prev] | [next] | [standalone]
| From | James Kuyper <jameskuyper@verizon.net> |
|---|---|
| Date | 2015-09-25 18:46 -0400 |
| Message-ID | <5605CEBA.7020109@verizon.net> |
| In reply to | #71204 |
On 09/25/2015 06:07 PM, Jorgen Grahn wrote: ... > It's funny -- and maybe I'm tempting fate by writing this -- but I've > done a lot of troubleshooting over the years. Rarely or never have I > been in a situation where the crash or error at time T was caused by a > bug at time T0, which I couldn't find. Just recently I spent a lot of time tracking down a bug, that led me deep into a third-party library. While provided as source code, understanding why it was failing required a detailed understanding of that library, which I don't have. I could see that the code was generating an invalid pointer, which caused a SIGSEGV when my own code attempted to dereference it, but I didn't understand why the generated pointer was invalid. When I contacted the third-party help desk, they were quite willing to help. However, getting my example code (which I simplified as much as possible - which wasn't anywhere near as much as I'd have liked) running on the their system required installing several other third-party libraries (every attempt I made to remove the dependence on one of those libraries caused the symptoms to disappear) which they were unfamiliar with. In the end, they found a fix that made their copy of my simplified example work - on their system. The same fix did NOT make my copy of the code work on my system. Security restrictions prevented us from setting up remote access to each other's systems, and travel budget restrictions prevented either of us from physically visiting the other company's offices. Very frustrating. > What I want to say is, I guess: yes, having gdb looking at the SEGV > doesn't mean you're looking at the bug ... but you should also not > give up. > > Finding the bug in such circumstances is fun and exciting, and a > valuable skill. Finding it can be fun; looking for it is often very far from fun, particularly with SIGSEGV problems.
[toc] | [prev] | [next] | [standalone]
| From | Ian Collins <ian-news@hotmail.com> |
|---|---|
| Date | 2015-09-26 10:57 +1200 |
| Message-ID | <d6m1quFqr3pU7@mid.individual.net> |
| In reply to | #71205 |
James Kuyper wrote: > On 09/25/2015 06:07 PM, Jorgen Grahn wrote: > .... >> It's funny -- and maybe I'm tempting fate by writing this -- but I've >> done a lot of troubleshooting over the years. Rarely or never have I >> been in a situation where the crash or error at time T was caused by a >> bug at time T0, which I couldn't find. > > Just recently I spent a lot of time tracking down a bug, that led me > deep into a third-party library. While provided as source code, > understanding why it was failing required a detailed understanding of > that library, which I don't have. I could see that the code was > generating an invalid pointer, which caused a SIGSEGV when my own code > attempted to dereference it, but I didn't understand why the generated > pointer was invalid. > When I contacted the third-party help desk, they were quite willing to > help. However, getting my example code (which I simplified as much as > possible - which wasn't anywhere near as much as I'd have liked) running > on the their system required installing several other third-party > libraries (every attempt I made to remove the dependence on one of those > libraries caused the symptoms to disappear) which they were unfamiliar > with. In the end, they found a fix that made their copy of my simplified > example work - on their system. The same fix did NOT make my copy of the > code work on my system. Security restrictions prevented us from setting > up remote access to each other's systems, and travel budget restrictions > prevented either of us from physically visiting the other company's > offices. Very frustrating. One option that I used recently to get around security restrictions was to build a VM with just enough installed to replicate the problem. The image was small enough (smaller than the kernel crash dump!) for the vendor to upload. -- Ian Collins
[toc] | [prev] | [next] | [standalone]
| From | Malcolm McLean <malcolm.mclean5@btinternet.com> |
|---|---|
| Date | 2015-09-25 21:40 -0700 |
| Message-ID | <98cfe991-82a6-4af5-bf2c-6f921418dba2@googlegroups.com> |
| In reply to | #71205 |
On Friday, September 25, 2015 at 11:46:41 PM UTC+1, James Kuyper wrote: > > Just recently I spent a lot of time tracking down a bug, that led me > deep into a third-party library. While provided as source code, > understanding why it was failing required a detailed understanding of > that library, which I don't have. I could see that the code was > generating an invalid pointer, which caused a SIGSEGV when my own code > attempted to dereference it, but I didn't understand why the generated > pointer was invalid. > When I contacted the third-party help desk, they were quite willing to > help. However, getting my example code (which I simplified as much as > possible - which wasn't anywhere near as much as I'd have liked) running > on the their system required installing several other third-party > libraries (every attempt I made to remove the dependence on one of those > libraries caused the symptoms to disappear) which they were unfamiliar > with. > That's essentially what Bart and I have been saying. Libraries take a lot of time to install and use. We need to find ways of keeping depenency hierarchies small and shallow.
[toc] | [prev] | [next] | [standalone]
| From | Ian Collins <ian-news@hotmail.com> |
|---|---|
| Date | 2015-09-26 16:51 +1200 |
| Message-ID | <d6mmj5Fqr3pU8@mid.individual.net> |
| In reply to | #71210 |
Malcolm McLean wrote: > On Friday, September 25, 2015 at 11:46:41 PM UTC+1, James Kuyper wrote: >> >> Just recently I spent a lot of time tracking down a bug, that led me >> deep into a third-party library. While provided as source code, >> understanding why it was failing required a detailed understanding of >> that library, which I don't have. I could see that the code was >> generating an invalid pointer, which caused a SIGSEGV when my own code >> attempted to dereference it, but I didn't understand why the generated >> pointer was invalid. >> When I contacted the third-party help desk, they were quite willing to >> help. However, getting my example code (which I simplified as much as >> possible - which wasn't anywhere near as much as I'd have liked) running >> on the their system required installing several other third-party >> libraries (every attempt I made to remove the dependence on one of those >> libraries caused the symptoms to disappear) which they were unfamiliar >> with. >> > That's essentially what Bart and I have been saying. > Libraries take a lot of time to install and use. We need to find ways > of keeping depenency hierarchies small and shallow. That's easy: reinvent everything yourself. -- Ian Collins
[toc] | [prev] | [next] | [standalone]
| From | Bartc <bc@freeuk.com> |
|---|---|
| Date | 2015-09-26 10:45 +0100 |
| Message-ID | <mu5pbp$mi5$1@dont-email.me> |
| In reply to | #71211 |
On 26/09/2015 05:51, Ian Collins wrote: > Malcolm McLean wrote: >> On Friday, September 25, 2015 at 11:46:41 PM UTC+1, James Kuyper wrote: >>> >>> Just recently I spent a lot of time tracking down a bug, that led me >>> deep into a third-party library. While provided as source code, >>> understanding why it was failing required a detailed understanding of >>> that library, which I don't have. I could see that the code was >>> generating an invalid pointer, which caused a SIGSEGV when my own code >>> attempted to dereference it, but I didn't understand why the generated >>> pointer was invalid. >>> When I contacted the third-party help desk, they were quite willing to >>> help. However, getting my example code (which I simplified as much as >>> possible - which wasn't anywhere near as much as I'd have liked) running >>> on the their system required installing several other third-party >>> libraries (every attempt I made to remove the dependence on one of those >>> libraries caused the symptoms to disappear) which they were unfamiliar >>> with. >>> >> That's essentially what Bart and I have been saying. >> Libraries take a lot of time to install and use. We need to find ways >> of keeping depenency hierarchies small and shallow. > > That's easy: reinvent everything yourself. That's not always an option, but you can a choose a library or dependency that gives less trouble. Example 1: until about 1995, I /did/ re-invent everything myself, software-wise (I stopped reinventing hardware in 1985!). Then I switched to Windows API. For all its faults, Win API is solid, and very stable (I'm still using the same API 20 years later). It's also guaranteed to exist on any platform using Windows, so there are no other dependencies to download. Example 2: I have a project where the output relies on a third party linker. Initially, I used gcc as the linker, but you can imagine this was a very big dependency (100s of MB) to download and install (especially if the 64-bit linker needed required gcc to be built from source, as nearly happened). Then I found I could forget gcc.exe, and directly use the linker itself ld.exe. Although it was harder to do, it was worth it (it doesn't automatically provide C's 'int main(nargs,args)' entry point for example). But it was still sizeable and untidy dependency: (ld.exe, libiconv.dll, libintl-8.dll, linwinpthread-1.dll, libz-1.dll, about 1.7MB). Someone would still need to download big chunks of gcc to get it, unless I could redistribute those files. Now it seems there is also a third-party linker which is a single 47KB executable. This ticks all the boxes: it's tiny, fast, and, if I can't bundle it, it is trivial to download. And if there's a problem, the author is available to answer questions! And yet a further option is to just write a linker and be done with it. End of problem. See, reinventing things can be very attractive! -- Bartc
[toc] | [prev] | [next] | [standalone]
| From | Malcolm McLean <malcolm.mclean5@btinternet.com> |
|---|---|
| Date | 2015-09-26 03:39 -0700 |
| Message-ID | <0e89f497-95c5-4551-ac3e-4376055c53e3@googlegroups.com> |
| In reply to | #71212 |
On Saturday, September 26, 2015 at 10:45:36 AM UTC+1, Bart wrote: > On 26/09/2015 05:51, Ian Collins wrote: > > Malcolm McLean wrote: > >> > >> That's essentially what Bart and I have been saying. > >> Libraries take a lot of time to install and use. We need to find ways > >> of keeping depenency hierarchies small and shallow. > > > > That's easy: reinvent everything yourself. > > That's not always an option, but you can a choose a library or > dependency that gives less trouble. > > Example 1: until about 1995, I /did/ re-invent everything myself, > software-wise (I stopped reinventing hardware in 1985!). Then I switched > to Windows API. > I'm developing Baby X to free my projects from Windows API. Currently I'm adding better graphics support. There's a project called NanoSVG which is open source, and it includes a rasteriser and an SVG parser, as pure C files. NanoSVG can be used as is in the resource compiler. So that's another image format Baby X RC supports. But I'm also going to build a graphics context round it. That will require a few changes to the source, but nothing much. But all the dependencies are flattened - NanoSVG is rolled into the Baby X code. It's a lot easier than writing my own rasteriser. And NanoSVG was based on freetype. That's how software reuse should work.
[toc] | [prev] | [next] | [standalone]
| From | Bartc <bc@freeuk.com> |
|---|---|
| Date | 2015-09-26 12:20 +0100 |
| Message-ID | <mu5uu7$9j3$1@dont-email.me> |
| In reply to | #71214 |
On 26/09/2015 11:39, Malcolm McLean wrote: > On Saturday, September 26, 2015 at 10:45:36 AM UTC+1, Bart wrote: >> On 26/09/2015 05:51, Ian Collins wrote: >>> Malcolm McLean wrote: >>>> >>>> That's essentially what Bart and I have been saying. >>>> Libraries take a lot of time to install and use. We need to find ways >>>> of keeping depenency hierarchies small and shallow. >>> >>> That's easy: reinvent everything yourself. >> >> That's not always an option, but you can a choose a library or >> dependency that gives less trouble. >> >> Example 1: until about 1995, I /did/ re-invent everything myself, >> software-wise (I stopped reinventing hardware in 1985!). Then I switched >> to Windows API. >> > I'm developing Baby X to free my projects from Windows API. I understand that BabyX also runs on Windows, so it still needs to use the API. Presumably you're then just using a layer on top of the Windows API. I do the same, but what I'm saying is that no-one needs to worry about downloading and installing the Windows API! (Compare with using WxWindows or GTK.) > Currently I'm adding better graphics support. There's a project > called NanoSVG which is open source, and it includes a rasteriser > and an SVG parser, as pure C files. > NanoSVG can be used as is in the resource compiler. So that's another > image format Baby X RC supports. But I'm also going to build a > graphics context round it. That will require a few changes to the > source, but nothing much. But all the dependencies are flattened > - NanoSVG is rolled into the Baby X code. > It's a lot easier than writing my own rasteriser. And NanoSVG was > based on freetype. That's how software reuse should work. My background in the past has been with low-end CAD software, where I did have to code all this stuff myself. I had no objection to later off-loading much of the work to libraries such as GDI, OpenGL and PostScript. They come with the platform for a start (inside the printer for PS). But then compare with DirectDraw which I've never been able to make head nor tail of. And with an API that relies on C++ on top. GDI might have been clunky to use but was at least understandable and accessible. -- Bartc
[toc] | [prev] | [next] | [standalone]
| From | Malcolm McLean <malcolm.mclean5@btinternet.com> |
|---|---|
| Date | 2015-09-26 06:39 -0700 |
| Message-ID | <4f06268c-a922-4059-8a79-f10f647de320@googlegroups.com> |
| In reply to | #71215 |
On Saturday, September 26, 2015 at 12:20:52 PM UTC+1, Bart wrote: > On 26/09/2015 11:39, Malcolm McLean wrote: > > > I'm developing Baby X to free my projects from Windows API. > > I understand that BabyX also runs on Windows, so it still needs to use > the API. Presumably you're then just using a layer on top of the Windows > API. > > I do the same, but what I'm saying is that no-one needs to worry about > downloading and installing the Windows API! (Compare with using > WxWindows or GTK.) > It's designed as a medium-thickness layer between the OS windowing system and the application. There also an X windows version. A lot of the functions just re-implement GDI controls - xlib is low level and doesn't have "buttons" or similar objects. As the name suggest, it was originally intended for X. > > But then compare with DirectDraw which I've never been able to make head > nor tail of. And with an API that relies on C++ on top. GDI might have > been clunky to use but was at least understandable and accessible. > GDI is nice and simple, but it's really only useful for very functional programs. My program Crossword Designer uses it, because constructing a crossword is a job of work, the user's not looking for lots of eye candy, just an interface that lets him get the crossword up and edited. But Senet is a game, it uses GDI, but just to blit rgba buffers constructed internally to the screen.
[toc] | [prev] | [next] | [standalone]
| From | fir <profesor.fir@gmail.com> |
|---|---|
| Date | 2015-09-27 01:45 -0700 |
| Message-ID | <c565c3c3-67f6-434c-9311-1305714c6645@googlegroups.com> |
| In reply to | #71211 |
W dniu sobota, 26 września 2015 06:52:01 UTC+2 użytkownik Ian Collins napisał: > Malcolm McLean wrote: > > On Friday, September 25, 2015 at 11:46:41 PM UTC+1, James Kuyper wrote: > >> > >> Just recently I spent a lot of time tracking down a bug, that led me > >> deep into a third-party library. While provided as source code, > >> understanding why it was failing required a detailed understanding of > >> that library, which I don't have. I could see that the code was > >> generating an invalid pointer, which caused a SIGSEGV when my own code > >> attempted to dereference it, but I didn't understand why the generated > >> pointer was invalid. > >> When I contacted the third-party help desk, they were quite willing to > >> help. However, getting my example code (which I simplified as much as > >> possible - which wasn't anywhere near as much as I'd have liked) running > >> on the their system required installing several other third-party > >> libraries (every attempt I made to remove the dependence on one of those > >> libraries caused the symptoms to disappear) which they were unfamiliar > >> with. > >> > > That's essentially what Bart and I have been saying. > > Libraries take a lot of time to install and use. We need to find ways > > of keeping depenency hierarchies small and shallow. > > That's easy: reinvent everything yourself. > nice to see such abandoned text of clear stupidity down in the dungeon ps check my post "low, medium, and high level coding or apis" on comp.programming as this is somewhat related
[toc] | [prev] | [next] | [standalone]
| From | "Morten W. Petersen" <morphex@gmail.com> |
|---|---|
| Date | 2015-09-26 23:11 +0200 |
| Message-ID | <mu71m5$rks$1@speranza.aioe.org> |
| In reply to | #71204 |
On 26.09.2015 00:07, Jorgen Grahn wrote: > On Fri, 2015-09-25, John Gordon wrote: >> In <mu29uk$iaf$1@speranza.aioe.org> "Morten W. Petersen" <morphex@gmail.com> writes: >> >>> The line that ends up in a SIGSEGV is >> >>> https://github.com/morphex/smash_xml/blob/6b558ae0347c04992d0f3c2306373a83d1c2765e/tests.c#L236 >> >> When you get a SEGV, it's often the case that the true cause of the error >> is much earlier in the program. The line of code that generates the SEGV >> may be perfectly innocent. > > It's funny -- and maybe I'm tempting fate by writing this -- but I've > done a lot of troubleshooting over the years. Rarely or never have I > been in a situation where the crash or error at time T was caused by a > bug at time T0, which I couldn't find. Detective work is usually > needed, and you need to reproduce the problem with changes to the > source code ... but it seems to me there have always been clues for me > to find. > > What I want to say is, I guess: yes, having gdb looking at the SEGV > doesn't mean you're looking at the bug ... but you should also not > give up. > > Finding the bug in such circumstances is fun and exciting, and a > valuable skill. Yes I imagine it is a good skill to have, and when the code around just calling a function is failing, it can't be anything else than something preceding that, that is the cause. I think the best place to start is to understand the output of Valgrind and then make alterations based on that. If that doesn't help, I'll comment out the different sections of the tests.c file to isolate the issue. -Morten
[toc] | [prev] | [next] | [standalone]
| From | jacobnavia <jacob@jacob.remcomp.fr> |
|---|---|
| Date | 2015-09-25 10:28 +0200 |
| Message-ID | <mu30f9$7jl$1@dont-email.me> |
| In reply to | #71186 |
Le 25/09/2015 04:02, Morten W. Petersen a écrit : > Hi there. > > Once again I'm working on the Smash XML project, and I'm getting a > SIGSEGV when calling a function. > > The line that ends up in a SIGSEGV is > > https://github.com/morphex/smash_xml/blob/6b558ae0347c04992d0f3c2306373a83d1c2765e/tests.c#L236 > > > And gdb says this after "make debug; gdb ./decode_xml": > > (gdb) run > [...] > test_parse_file > > Program received signal SIGSEGV, Segmentation fault. > __chkstk_ms () at > /usr/src/debug/gcc-4.9.3-1/libgcc/config/i386/cygwin.S:172 Excuse me but that is not your program but the source code of gcc itself... Unless your software lives in the gcc-4.9.3-1 that code is not you but gdb. > 172 orl $0x0, (%ecx) /* probe there */ > (gdb) print $ecx > $1 = 600600 > (gdb) > This code is trying to figure out if ecx is != from NULL. Under windows the ecx register has the first argument to a function, in this case a FILE *. > So somewhere between the function call and this line > > https://github.com/morphex/smash_xml/blob/6b558ae0347c04992d0f3c2306373a83d1c2765e/decode_xml.c#L1020 > > Put a breakpoint before the call. The go in machine step by step until you arrive at the called function: command: "stepi" for going instruction by instruction command: "x/5i $rip" displays the 5 next instructions beginning with the current program counter command: "display $rcx" will print the contents of rcs at each assembly step Have fun!
[toc] | [prev] | [next] | [standalone]
| From | Jorgen Grahn <grahn+nntp@snipabacken.se> |
|---|---|
| Date | 2015-09-25 10:33 +0000 |
| Message-ID | <slrnn0a8og.eij.grahn+nntp@frailea.sa.invalid> |
| In reply to | #71189 |
On Fri, 2015-09-25, jacobnavia wrote: > Le 25/09/2015 04:02, Morten W. Petersen a écrit : >> Hi there. >> >> Once again I'm working on the Smash XML project, and I'm getting a >> SIGSEGV when calling a function. >> >> The line that ends up in a SIGSEGV is >> >> https://github.com/morphex/smash_xml/blob/6b558ae0347c04992d0f3c2306373a83d1c2765e/tests.c#L236 >> >> >> And gdb says this after "make debug; gdb ./decode_xml": >> >> (gdb) run >> [...] >> test_parse_file >> >> Program received signal SIGSEGV, Segmentation fault. >> __chkstk_ms () at >> /usr/src/debug/gcc-4.9.3-1/libgcc/config/i386/cygwin.S:172 > > > Excuse me but that is not your program but the source code of gcc itself... > > Unless your software lives in the gcc-4.9.3-1 that code is not you but gdb. Yes; the OP needs to learn a bit more about his debugger. The first thing I do at this point is "bt" (print the stack trace) and "up"/"down" (navigate it). All other advice people have given also applies. One more: try to run the program with valgrind, if it's available for your platform. It might (if you're lucky) trigger when the problem is created, rather than when it manifests itself as a segfault. /Jorgen -- // Jorgen Grahn <grahn@ Oo o. . . \X/ snipabacken.se> O o .
[toc] | [prev] | [next] | [standalone]
| From | "Morten W. Petersen" <morphex@gmail.com> |
|---|---|
| Date | 2015-09-25 14:05 +0200 |
| Message-ID | <mu3d97$rjr$1@speranza.aioe.org> |
| In reply to | #71191 |
On 25.09.2015 12:33, Jorgen Grahn wrote: > On Fri, 2015-09-25, jacobnavia wrote: >> Le 25/09/2015 04:02, Morten W. Petersen a écrit : >>> Hi there. >>> >>> Once again I'm working on the Smash XML project, and I'm getting a >>> SIGSEGV when calling a function. >>> >>> The line that ends up in a SIGSEGV is >>> >>> https://github.com/morphex/smash_xml/blob/6b558ae0347c04992d0f3c2306373a83d1c2765e/tests.c#L236 >>> >>> >>> And gdb says this after "make debug; gdb ./decode_xml": >>> >>> (gdb) run >>> [...] >>> test_parse_file >>> >>> Program received signal SIGSEGV, Segmentation fault. >>> __chkstk_ms () at >>> /usr/src/debug/gcc-4.9.3-1/libgcc/config/i386/cygwin.S:172 >> >> >> Excuse me but that is not your program but the source code of gcc itself... >> >> Unless your software lives in the gcc-4.9.3-1 that code is not you but gdb. > > Yes; the OP needs to learn a bit more about his debugger. The first > thing I do at this point is "bt" (print the stack trace) and > "up"/"down" (navigate it). I wasn't aware of up/down but had tried out bt/frame and maximal gdb settings when compiling. So it seems like the stack is indeed mangled. > One more: try to run the program with valgrind, if it's available for > your platform. It might (if you're lucky) trigger when the problem is > created, rather than when it manifests itself as a segfault. Yes. I'll switch over to Linux and test with Valgrind, it has given some messages, just have to learn understanding and using it first. -Morten
[toc] | [prev] | [next] | [standalone]
| From | Jorgen Grahn <grahn+nntp@snipabacken.se> |
|---|---|
| Date | 2015-09-25 16:44 +0000 |
| Message-ID | <slrnn0aug8.eij.grahn+nntp@frailea.sa.invalid> |
| In reply to | #71193 |
On Fri, 2015-09-25, Morten W. Petersen wrote: > On 25.09.2015 12:33, Jorgen Grahn wrote: ... >> One more: try to run the program with valgrind, if it's available for >> your platform. It might (if you're lucky) trigger when the problem is >> created, rather than when it manifests itself as a segfault. > > Yes. I'll switch over to Linux and test with Valgrind, it has given > some messages, just have to learn understanding and using it first. Good! It's not difficult: it's typically a bunch of stack traces like "here you allocated 52 bytes" and "here you wrote 8 bytes past the end of that block". /Jorgen -- // Jorgen Grahn <grahn@ Oo o. . . \X/ snipabacken.se> O o .
[toc] | [prev] | [next] | [standalone]
Page 1 of 17 [1] 2 3 … 17 Next page →
Back to top | Article view | comp.lang.c
csiph-web