![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 10/1/2010 8:10 PM, Darren New wrote:
> Mike Raiford wrote:
>> The way software around here is written makes me want to poke my eyes
>> out. Today is one of those days.
>
> Let me know when you're debugging assertion errors in library code for
> which you don't have the source, and for which the include files don't
> match the declarations in the .so files, and for which there isn't
> enough memory to run the code under the debugger.
>
Eh... I'm sure you can do machine-level stepping, at least. ;)
--
~Mike
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Mike Raiford wrote:
> Eh... I'm sure you can do machine-level stepping, at least. ;)
Nope. Indeed, the whole system is set up to prevent being debugged.
I suppose if we built a special unsigned build and spent a few dozen grand
per developer on a JTAG we could figure out how to do it.
--
Darren New, San Diego CA, USA (PST)
Serving Suggestion:
"Don't serve this any more. It's awful."
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Darren New escreveu:
> Mike Raiford wrote:
>> Eh... I'm sure you can do machine-level stepping, at least. ;)
>
> Nope. Indeed, the whole system is set up to prevent being debugged.
see why proprietary software is evil? ;)
--
a game sig: http://tinyurl.com/d3rxz9
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
nemesis wrote:
> Darren New escreveu:
>> Mike Raiford wrote:
>>> Eh... I'm sure you can do machine-level stepping, at least. ;)
>>
>> Nope. Indeed, the whole system is set up to prevent being debugged.
>
> see why proprietary software is evil? ;)
>
It's not proprietary software per se. It's DRM. Oh, and the fact that much
of the interesting code doesn't actually run on the CPU as such.
--
Darren New, San Diego CA, USA (PST)
Serving Suggestion:
"Don't serve this any more. It's awful."
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 10/4/2010 4:10 PM, Darren New wrote:
> It's not proprietary software per se. It's DRM. Oh, and the fact that
DRM sucks. :P
--
~Mike
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Mike Raiford wrote:
> On 10/4/2010 4:10 PM, Darren New wrote:
>
>> It's not proprietary software per se. It's DRM. Oh, and the fact that
>
> DRM sucks. :P
Explaining to your boss why even if he gives you all the files, you still
can't figure out why it went wrong this one time... that's what sucks.
--
Darren New, San Diego CA, USA (PST)
Serving Suggestion:
"Don't serve this any more. It's awful."
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 10/5/2010 10:47 AM, Darren New wrote:
> Mike Raiford wrote:
>> On 10/4/2010 4:10 PM, Darren New wrote:
>>
>>> It's not proprietary software per se. It's DRM. Oh, and the fact that
>>
>> DRM sucks. :P
>
> Explaining to your boss why even if he gives you all the files, you
> still can't figure out why it went wrong this one time... that's what
> sucks.
>
A situation in which, if it weren't for DRM, you wouldn't be in... ;P
--
~Mike
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Mike Raiford wrote:
> On 10/5/2010 10:47 AM, Darren New wrote:
>> Mike Raiford wrote:
>>> On 10/4/2010 4:10 PM, Darren New wrote:
>>>
>>>> It's not proprietary software per se. It's DRM. Oh, and the fact that
>>>
>>> DRM sucks. :P
>>
>> Explaining to your boss why even if he gives you all the files, you
>> still can't figure out why it went wrong this one time... that's what
>> sucks.
>>
>
> A situation in which, if it weren't for DRM, you wouldn't be in... ;P
Well, yes. I wasn't arguing, there. :-)
Now I'm having fun of "that company says they serve media like *this*, so I
need to write code to read *this*." "Have you actually seen the media?
Because that type of media can't be served the way you say." "No, I'm
waiting for a URL, but I'm half done writing the code."
Right up there with "Can you fix the bug with *that* media format?" "Do you
have any samples that actually trigger the bug, because the code itself
looks like it handles the condition." "No, no samples, but people are
telling me it doesn't work."
--
Darren New, San Diego CA, USA (PST)
Serving Suggestion:
"Don't serve this any more. It's awful."
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 10/5/2010 11:57 AM, Darren New wrote:
> Right up there with "Can you fix the bug with *that* media format?" "Do
> you have any samples that actually trigger the bug, because the code
> itself looks like it handles the condition." "No, no samples, but people
> are telling me it doesn't work."
Lovely ... You win :)
--
~Mike
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Mike Raiford wrote:
> On 10/5/2010 11:57 AM, Darren New wrote:
>
>> Right up there with "Can you fix the bug with *that* media format?" "Do
>> you have any samples that actually trigger the bug, because the code
>> itself looks like it handles the condition." "No, no samples, but people
>> are telling me it doesn't work."
>
> Lovely ... You win :)
For some hitherto unknown meaning of the word "win" I suppose.
And today I'm dealing with "Remember that DRM failure that you said was due
to a broken six-month-old license, where you posted the broken license with
the embedded dates and the working license in the bug report reply? Well, it
was a new-release movie. I have the purchase history to show it."
Not unlike "Yes, I know the gauge is on E, and the car won't start, but
look, I have a credit card receipt from gas station up the road dated just
yesterday!"
--
Darren New, San Diego CA, USA (PST)
Serving Suggestion:
"Don't serve this any more. It's awful."
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |