Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c > #54991

Re: C program. run time abend, range fault.

Show all headers | View raw

On 12/18/2014 02:38 PM, Shiva wrote:
...
>> What makes it so difficult to simply cut and paste the actual code
>> that compiled and malfunctioned into your posted message? What
>> produces this strange compulsion to generate  an error-filled hand
>> copy of the code?
> 
> Kenny got point one and three fine. But there's a more important and
> more explaining answer to that. I hope you have offshore colleagues?
> I hope you have Indian contractors working for 'partner' companies
> contracted to your company? If not, what I'm going to tell you might
> look like a made up story, but trust me - it is not.

I work in a very different environment from yours. We don't outsource
any of our own code, but we do receive code from dozens of science teams
all around the world that we're required to integrate into our system.

> I don't know about the other occurrences that you were saying about,
> but in this instance - I work from India (of course, the outsourcing
> debate comes up right here) in one such partner company to a very,
> very reputed European client whose name I cannot disclose here due to
> legal restrictions.
> 
> In my workplace, we have rules. Better read that as strict rules. I'm
> not allowed to take camera mobiles to my workplace. I'm not allowed
> to take a piece of paper inside, and even if I did - definitely can't
> bring it back outside the office. Strict rules, 24x7 monitored. And
> there's near to zero internet access in my workplace. If I develop a
> code and I face an issue and I want to google an answer for it, I
> don't get an opportunity to open all the results that google provides
> me. 9 out of those 10 results would come up as blocked sites for me.
> So everytime I face an issue, I have to steal a part of my own
> (faulty) code and come back home with that piece of paper and google
> it then and try to find a solution to make it work the next day. If
> you had seen my replies above, they'd validate that I've been
> answering questions only after the indian day time. Only during
> nights when I come home. It's not that I don't want to copy paste my
> code. Forget the legal restrictions there, I'm well past that when I
> first posted a similar kind of code to post the question here in the
> first place. To post my code here I've painfully write every single
> line of it in a piece of paper that can be accommodated in my pocket
> without any notice and I come back home to type it all up from that
> paper again and post it.

Again, I work in a very different environment. Since we do civilian
scientific data processing, all of our science code is required to be
freely available to the general scientific public, so it can be subject
to review by other scientists to confirm whether it does what it's
supposed to do. Open source is the norm in our world, not the exception.
Our production system code is not publicly available, but only because
it's of no outside interest - there's nothing sensitive about it.

Some of the work I do involves purely civilian applications of data
collected by a satellite that is shared between NASA, NOAA, and the
Department of Defense. Because of the DoD involvement, even though I
know nothing about how the DoD uses that satellite, that code is subject
to export restrictions, and is therefore not publicly available, but
that's a rare thing in my working environment. I can't imagine how a
foreign agent could make use of any of that code to harm the US - but
I've often found my imagination to be lacking.

...
> So finally, I'm still going to try and correct the code above, I'm
> really sorry - I won't force you to help me, nor any of you, I'll try
> my best here and if there's no body here to respond, I'd understand.
> I just want to give it a try. I'm really sorry for all the grievances
> caused.

Some parts of what you describe are reasonable approaches to keeping
proprietary code secure. But they go too far in restricting your ability
to seek useful help. In the long run, that will help ensure that the
code you write won't be worth stealing - which, I suppose, is another
way to discourage theft :-}

There should be a way to sanitize failed code so it contains no
proprietary information, while still demonstrating the problem that
needs to be solved. It should be possible to get permission to post that
sanitized code in places like this, in order to get help. Alternatively,
if your workplace is large enough, it should have a internal location
where you can go to for help, without worrying about such issues - but
that requires that your company hire at least a few guru-level
programmers, and those are very expensive, for good reasons. If you have
management that is open to suggestions (I won't be surprised if they
aren't), I recommend suggesting these things - your company would be
better for it.

Do you have, at home, a system capable of compiling the "stolen" code
you brought home? In particular, do you have a home system sufficiently
similar to your work system that it allows you to duplicate the problem
you've reported? If so, take your "stolen" code, and work with it on
your home system until you've got a version that compiles and executes,
producing the same problematic behavior you saw at work. Then post the
following:

* The exact code you compiled.
* Identification of the compiler you're using, and of the compile/link
options you chose.
* All of the evidence produced by your program indicating that it
failed. If it produced error messages, cut and past those messages into
your posting.

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

C program. run time abend, range fault. Shiva <subramanian.klu@gmail.com> - 2014-12-16 00:47 -0800
  Re: C program. run time abend, range fault. jt@toerring.de (Jens Thoms Toerring) - 2014-12-16 10:31 +0000
    Re: C program. run time abend, range fault. Shiva <subramanian.klu@gmail.com> - 2014-12-16 11:33 -0800
      Re: C program. run time abend, range fault. Barry Schwarz <schwarzb@dqel.com> - 2014-12-16 14:27 -0800
      Re: C program. run time abend, range fault. jt@toerring.de (Jens Thoms Toerring) - 2014-12-16 23:08 +0000
      Re: C program. run time abend, range fault. Ben Bacarisse <ben.usenet@bsb.me.uk> - 2014-12-16 23:44 +0000
    Re: C program. run time abend, range fault. glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2014-12-16 19:37 +0000
      Re: C program. run time abend, range fault. jt@toerring.de (Jens Thoms Toerring) - 2014-12-17 00:12 +0000
        Re: C program. run time abend, range fault. Shiva <subramanian.klu@gmail.com> - 2014-12-17 13:05 -0800
          Re: C program. run time abend, range fault. Barry Schwarz <schwarzb@dqel.com> - 2014-12-17 15:06 -0800
            Re: C program. run time abend, range fault. Richard Heathfield <invalid@see.sig.invalid> - 2014-12-17 23:15 +0000
              Re: C program. run time abend, range fault. Keith Thompson <kst-u@mib.org> - 2014-12-17 16:00 -0800
            Re: C program. run time abend, range fault. Keith Thompson <kst-u@mib.org> - 2014-12-17 15:56 -0800
            Re: C program. run time abend, range fault. Shiva <subramanian.klu@gmail.com> - 2014-12-18 12:28 -0800
              Re: C program. run time abend, range fault. Barry Schwarz <schwarzb@dqel.com> - 2014-12-18 14:07 -0800
              Re: C program. run time abend, range fault. Barry Schwarz <schwarzb@dqel.com> - 2014-12-18 14:16 -0800
              Re: C program. run time abend, range fault. jacob navia <jacob@spamsink.net> - 2014-12-19 00:55 +0100
              Re: C program. run time abend, range fault. jt@toerring.de (Jens Thoms Toerring) - 2014-12-19 00:18 +0000
              Re: C program. run time abend, range fault. Ben Bacarisse <ben.usenet@bsb.me.uk> - 2014-12-19 01:12 +0000
          Re: C program. run time abend, range fault. jt@toerring.de (Jens Thoms Toerring) - 2014-12-18 01:00 +0000
          Re: C program. run time abend, range fault. James Kuyper <jameskuyper@verizon.net> - 2014-12-17 22:29 -0500
            Re: C program. run time abend, range fault. gazelle@shell.xmission.com (Kenny McCormack) - 2014-12-18 09:18 +0000
              Re: C program. run time abend, range fault. Martin Shobe <martin.shobe@yahoo.com> - 2014-12-18 11:10 -0600
                Re: C program. run time abend, range fault. Shiva <subramanian.klu@gmail.com> - 2014-12-18 11:38 -0800
                Re: C program. run time abend, range fault. James Kuyper <jameskuyper@verizon.net> - 2014-12-18 15:24 -0500
                Re: C program. run time abend, range fault. Shiva <subramanian.klu@gmail.com> - 2014-12-18 12:37 -0800
  C program. run time abend, range fault. asetofsymbols@gmail.com - 2014-12-18 22:21 -0800
  Re: C program. run time abend, range fault. Is this the correct solution? jacob navia <jacob@spamsink.net> - 2014-12-19 18:32 +0100
    Re: C program. run time abend, range fault. Is this the correct solution? jacob navia <jacob@spamsink.net> - 2014-12-20 11:34 +0100
      Re: C program. run time abend, range fault. Is this the correct solution? Shiva <subramanian.klu@gmail.com> - 2014-12-31 11:48 -0800
        Re: C program. run time abend, range fault. Is this the correct solution? James Kuyper <jameskuyper@verizon.net> - 2014-12-31 15:49 -0500
        Re: C program. run time abend, range fault. Is this the correct solution? Keith Thompson <kst-u@mib.org> - 2014-12-31 13:07 -0800
          Re: C program. run time abend, range fault. Is this the correct solution? Geoff <geoff@invalid.invalid> - 2014-12-31 13:57 -0800
            Re: C program. run time abend, range fault. Is this the correct solution? Keith Thompson <kst-u@mib.org> - 2014-12-31 16:02 -0800
              Re: C program. run time abend, range fault. Is this the correct solution? Malcolm McLean <malcolm.mclean5@btinternet.com> - 2014-12-31 22:55 -0800
            Re: C program. run time abend, range fault. Is this the correct solution? raltbos@xs4all.nl (Richard Bos) - 2015-01-05 14:56 +0000
        Re: C program. run time abend, range fault. Is this the correct solution? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2014-12-31 21:51 +0000
        Re: C program. run time abend, range fault. Is this the correct solution? jacob navia <jacob@spamsink.net> - 2015-01-01 02:51 +0100
          Re: C program. run time abend, range fault. Is this the correct solution? raltbos@xs4all.nl (Richard Bos) - 2015-01-05 15:00 +0000
            Re: C program. run time abend, range fault. Is this the correct solution? Shiva <subramanian.klu@gmail.com> - 2015-01-05 09:45 -0800
              Re: C program. run time abend, range fault. Is this the correct solution? Geoff <geoff@invalid.invalid> - 2015-01-05 11:02 -0800
                Re: C program. run time abend, range fault. Is this the correct solution? Shiva <subramanian.klu@gmail.com> - 2015-01-06 10:33 -0800
                Re: C program. run time abend, range fault. Is this the correct solution? James Kuyper <jameskuyper@verizon.net> - 2015-01-06 14:09 -0500
                Re: C program. run time abend, range fault. Is this the correct solution? Shiva <subramanian.klu@gmail.com> - 2015-01-06 12:32 -0800
                Re: C program. run time abend, range fault. Is this the correct solution? James Kuyper <jameskuyper@verizon.net> - 2015-01-06 15:47 -0500
                Re: C program. run time abend, range fault. Is this the correct solution? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-01-06 23:58 +0000
                Re: C program. run time abend, range fault. Is this the correct solution? glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-01-07 04:31 +0000
                Re: C program. run time abend, range fault. Is this the correct solution? Robert Wessel <robertwessel2@yahoo.com> - 2015-01-06 23:36 -0600
                Re: C program. run time abend, range fault. Is this the correct solution? Richard Heathfield <invalid@see.sig.invalid> - 2015-01-07 07:08 +0000
                Re: C program. run time abend, range fault. Is this the correct solution? Shiva <subramanian.klu@gmail.com> - 2015-01-09 13:46 -0800
            Re: C program. run time abend, range fault. Is this the correct solution? Geoff <geoff@invalid.invalid> - 2015-01-05 09:56 -0800
  Re: C program. run time abend, range fault. Geoff <geoff@invalid.invalid> - 2015-01-01 14:38 -0800

csiph-web