POV-Ray : Newsgroups : povray.off-topic : Wahahahaha! Server Time
22 Nov 2026 12:13:31 EST (-0500)
  Wahahahaha! (Message 121 to 170 of 170)  
<<< Previous 50 Messages Goto Initial 50 Messages
From: Invisible
Subject: Re: Wahahahaha!
Date: 9 Nov 2007 04:33:02
Message: <4734294e$1@news.povray.org>
Stephen wrote:

> Well if we are going for a P***ing contest:)
> I built my first computer before I went to high school (11 – 12 yrs). It used a
> uniselector and a rotary phone dial. It could add and subtract with the output
> in binary. Almost as much fun as the wine making.

Um... technically that's not a stored-program computer. :-P


Post a reply to this message

From: Invisible
Subject: Re: Wahahahaha!
Date: 9 Nov 2007 04:34:25
Message: <473429a1$1@news.povray.org>
Jim Henderson wrote:
> On Thu, 08 Nov 2007 18:20:39 +0000, Orchid XP v7 wrote:
> 
>> Nicolas Alvarez wrote:
>>> Invisible escribió:
>>>> (I never really understood why programs produce core dumps. I mean,
>>>> seriously. What chance is there of anybody *ever* deducing anything
>>>> useful from this data? 10^-78?)
>>> The original programmer with access to the sourcecode *can* deduce data
>>> from it.
>> I seriously doubt it...
> 
> I've done it, several times, even with things I'm not the original 
> programmer for but have access to the source code.

Really?

Well, it still sounds absurdly improbable to me, but I'll take your word 
for it.

Now, how about that Windoze habit of saying "The program has experienced 
an error and will be shut down. Do you want to send debugging 
information?" What do you estimate the chances are that *anybody* will 
do anything at all with the data thus sent? ;-)


Post a reply to this message

From: Stephen
Subject: Re: Wahahahaha!
Date: 9 Nov 2007 05:30:00
Message: <web.473435f66f9d6136726bd13c0@news.povray.org>
Invisible <voi### [at] devnull> wrote:
> Stephen wrote:
>
> > Well if we are going for a P***ing contest:)
> > I built my first computer before I went to high school (11 – 12 yrs). It used a
> > uniselector and a rotary phone dial. It could add and subtract with the output
> > in binary. Almost as much fun as the wine making.
>
> Um... technically that's not a stored-program computer. :-P

I think really it was an electro mechanical abacus. It had two hard wired
programmes, add and subtract. :) You had to throw a switch to change the
operation.

Stephen


Post a reply to this message

From: Invisible
Subject: Re: Wahahahaha!
Date: 9 Nov 2007 06:07:56
Message: <47343f8c$1@news.povray.org>
Stephen wrote:
> Invisible <voi### [at] devnull> wrote:
>> Stephen wrote:
>>
>>> Well if we are going for a P***ing contest:)
>>> I built my first computer before I went to high school (11 – 12 yrs). It used a
>>> uniselector and a rotary phone dial. It could add and subtract with the output
>>> in binary. Almost as much fun as the wine making.
>> Um... technically that's not a stored-program computer. :-P
> 
> I think really it was an electro mechanical abacus. It had two hard wired
> programmes, add and subtract. :) You had to throw a switch to change the
> operation.

The word you're looking for is "calculator". ;-)

And what, you couldn't throw in a few extra logic circuits to convert 
from binary to decimal? ;-)

I, on the other hand, spent months designing CPU and some RAM circuits 
on my Amiga 1200 using DPaint IV AGA. I'm not really sure if it would 
ever have worked, but (without the RAM) would have required roughly 200 
chips. (7400, A.K.A. TTL quad 2-input NAND.)

I tried to restart that effort using KLogic - but it crashes too much.


Post a reply to this message

From: Stephen
Subject: Re: Wahahahaha!
Date: 9 Nov 2007 07:40:00
Message: <web.473454e06f9d6136726bd13c0@news.povray.org>
Invisible <voi### [at] devnull> wrote:
> Stephen wrote:
> > Invisible <voi### [at] devnull> wrote:
> >> Stephen wrote:
> >>
> >>> Well if we are going for a P***ing contest:)
> >>> I built my first computer before I went to high school (11 – 12 yrs). It used a
> >>> uniselector and a rotary phone dial. It could add and subtract with the output
> >>> in binary. Almost as much fun as the wine making.
> >> Um... technically that's not a stored-program computer. :-P
> >
> > I think really it was an electro mechanical abacus. It had two hard wired
> > programmes, add and subtract. :) You had to throw a switch to change the
> > operation.
>
> The word you're looking for is "calculator". ;-)
>
> And what, you couldn't throw in a few extra logic circuits to convert
> from binary to decimal? ;-)
>
> I, on the other hand, spent months designing CPU and some RAM circuits
> on my Amiga 1200 using DPaint IV AGA. I'm not really sure if it would
> ever have worked, but (without the RAM) would have required roughly 200
> chips. (7400, A.K.A. TTL quad 2-input NAND.)
>
> I tried to restart that effort using KLogic - but it crashes too much.

True, but to an eleven year old in the early 60’s it was only one step away from
Tobor the Robot :)
It was also before LCD’s although the Nixie tube was around. Can you design a
binary to decimal converter using only relay logic?
Ah! TTL, I built a digital clock out of TTL but did not put it together when I
checked the current. The PSU would have needed to supply 100 amps at 5 volts
Vcc. That was in the mid 70’s. In the late 70’s I built a clock with CMOS that
could run on a PP3 battery.


Stephen


Post a reply to this message

From: Warp
Subject: Re: Wahahahaha!
Date: 9 Nov 2007 07:50:25
Message: <47345791@news.povray.org>
Darren New <dne### [at] sanrrcom> wrote:
> Most other languages don't futz with the class of the object while it's 
> being constructed, so it doesn't really come up, I guess. One of the 
> costs of multiple inheritance as implemented by C++?

  I don't understand what multiple inheritance has to do with this.

-- 
                                                          - Warp


Post a reply to this message

From: Warp
Subject: Re: Wahahahaha!
Date: 9 Nov 2007 07:54:26
Message: <47345881@news.povray.org>
Invisible <voi### [at] devnull> wrote:
> Presumably that means that if you do sufficiently freaky things with 
> pointers to pointers to data through multiple levels of type casts, the 
> compiler can't figure out what you're actually doing or something.

  Or you simply have a regular function in the base class, this function
gets called in the initialization list of the base class constructor, and
in the implementation of this function you call a pure virtual function.

  It would be difficult for the compiler to follow how the functions are
being called (and, in fact, it's impossible for it to know if the pure
virtual function actually gets called in the general case).

  The problem with calling a pure virtual function in the base class
constructor is that the derived class has yet not been initialized and
thus calling a derived class function implementation could cause undefined
behavior because it's not constructed.

-- 
                                                          - Warp


Post a reply to this message

From: Invisible
Subject: Re: Wahahahaha!
Date: 9 Nov 2007 07:57:16
Message: <4734592c@news.povray.org>
Warp wrote:

>   The problem with calling a pure virtual function in the base class
> constructor is that the derived class has yet not been initialized and
> thus calling a derived class function implementation could cause undefined
> behavior because it's not constructed.

Um... probably. You know way more about C++ than I ever will.

Either way, it's definitely a program bug, and it's definitely 
completely unrelated to virtual memory. ;-)


Post a reply to this message

From: Warp
Subject: Re: Wahahahaha!
Date: 9 Nov 2007 08:05:30
Message: <47345b19@news.povray.org>
Invisible <voi### [at] devnull> wrote:
> Either way, it's definitely a program bug, and it's definitely 
> completely unrelated to virtual memory. ;-)

  That person is presenting the classical symptoms of clueless user whose
brain functions get diminished by 90% when in the precense of a computer.

  One typical symptom is the complete inability to read and understand
simple error or message dialogs. Typically from a message containing 12
words they see 2 and make all kinds of weird conclusions based on these
2 isolated random words.

  The symptoms are worsened when in precense of a knowledgeable person who
is trying (futilely) to teach them how to use the computer. The most typical
(and annoying) thing they will do is, when presented with a dialog with a
simple message and one single button ("Ok"), to ask "what do I do now?"
The mere precense of the knowledgeable person makes them completely blind
to the message in the dialog. They see random symbols which could as well
be chinese kanji.

-- 
                                                          - Warp


Post a reply to this message

From: Invisible
Subject: Re: Wahahahaha!
Date: 9 Nov 2007 08:15:21
Message: <47345d69$1@news.povray.org>
Warp wrote:
> Invisible <voi### [at] devnull> wrote:
>> Either way, it's definitely a program bug, and it's definitely 
>> completely unrelated to virtual memory. ;-)
> 
>   That person is presenting the classical symptoms of clueless user whose
> brain functions get diminished by 90% when in the precense of a computer.

In this particular person's case, I'd say more like a reduction of 60%. 
But that's still quite a big reduction, I'm sure you'll agree...

It seems to be a case of somebody seeing

   Microsoft VisualC++ Runtime Library
   A pure virtual function call occurred in SVCHOST.EXE.

and instead read it as

   La la la, la la, la la la *virtual* la la, la la la, la la.

This is probably not helped by the "engineer" who was supposed to be 
working on the equipment that this software runs. Apparently he saw this 
message and proclaimed "oh, your computer doesn't have enough virutal 
memory", and increased the setting from 250 MB to 2500 MB. (I.e., over 2GB.)

Ever since that time, nobody will believe me that the error message has 
nothing to do with virtual memory. Or rather, I explain that it's 
nothing to do with virtual memory, they go "oh, OK", and then a few days 
later they're asking me what I'm going to do about the virtual memory 
error that keeps happening. *sigh*

I guess you could classify that as a memory fault rather than a 
comprehension fault. I mean, when I explain that it's not virtual 
memory, they seem to kind of not really understand but never the less 
accept that what I'm saying is right. They just don't *remember* about it...

Oh, and if I find that "engineer", I'm going to give him a talking to. 
But, apparently, I'll have to join the queue first.

[Long story. Rather than getting the manufacturers to service our 
devices, we're using some El Cheapo company who's staff don't seem to 
really know what they're doing, and who take multiple visits to fix 
anything. Everybody is very exasperated, but we have been told by HQ 
that we can't use the manufacturers for cost reasons...]


Post a reply to this message

From: Brian Elliott
Subject: Re: Wahahahaha!
Date: 9 Nov 2007 10:57:05
Message: <47348351@news.povray.org>
"Arttu Voutilainen" <bli### [at] removethiszbxtnetinvalid> wrote in message 
news:47337108$1@news.povray.org...
> Eero Ahonen wrote:
>> Brian Elliott wrote:
>>> "Alain" <ele### [at] netscapenet> wrote in message
>>> news:4731f3f7$1@news.povray.org...
>>>> Once when playing with a small speaker, I pluged it in a transformer
>>>> and was prety unimpressed by the feeble low hum I got, so, I plugged
>>>> it directly into the wall socket, hoping for a loud hum. Use a regular
>>>> electrical plug, hook the speaker whires in to it, plug it in. Instant
>>>> POF, flash of light, small cloud of smoke, smell of ozone and burnt
>>>> metal, bursted speaker's dome. The coil's whires got vaporised.
>>>> At the time, I was about 10 or 11.
>>> I did the same to one of those tiny 3-volt DC motors, like the cog-ended
>>> ones that are in battery-powered toys.  A friend bragged at school he'd
>>> plugged one into the mains, and it went really incredibly fast and was
>>> really hot afterwards.
>>>
>>
>> Every time I read these I feel more and more sorry for myself for NOT
>> doing something that stupid (and cool :p) as a kid.
>>
>
> Yeah, me too.
>
> Guess I have still some time left to do something cool with elec ;)

Something cool to do as a bigger kid.

Rat the Extra-High-Tension transformer out of an old junked CRT-type TV or 
monitor.  (That weird-looking gangly thing covered in large amounts of black 
wax, with the *heavily" insulated wire from its top, that plugs into the 
back of the Cathode Ray tube)

Using an ohmmeter, you can determine which wire is the other side of the HT 
coil, and which wires are the low-voltage coil (they'll have less 
resistance, and maybe even a centre-tap point)

Fashion up a convenient 555 timer circuit on a 12-volt plugpack.  Tune it to 
about 16 kHz.  (or just go for "high squeal like a TV" set).  Buffer its 
output with either a single-ended, or for more efficiency, a push-pull power 
transistor output stage.  A naked 2N3055 will do fine, but you can use a 
smaller power transistor if you bolt it onto a heatsink.  Remember to put 
reverse-biased power diodes across the output transistor to soak up the 
back-EMF from the primary coil or you'll probably fritz your transistor 
pretty quick.

Eg. Assuming you have an NPN power transistor with emitter to Ground, bung 
its collector in series with the low-Volt primary winding to the 12 Volt 
rail.  Now, you need...

One clear 240-Volt tungsten incandescent bulb, but with a popped filament. 
It needs to have enough filament intact that there isn't too big a gap.

Hook the bulb up to the HT side of the transformer, turn the whole kaboodle 
on, and with a little luck, the bulb will display a lovely pinkish-violet 
ionised argon "flame" between the filament ends.  It'll should have enough 
energy to make the filament red hot and the glass hot above the convective 
"flame".


Post a reply to this message

From: Invisible
Subject: Re: Wahahahaha!
Date: 9 Nov 2007 11:05:23
Message: <47348543$1@news.povray.org>
Brian Elliott wrote:

> Rat the Extra-High-Tension transformer out of an old junked CRT-type TV 
> or monitor.  (That weird-looking gangly thing covered in large amounts 
> of black wax, with the *heavily" insulated wire from its top, that plugs 
> into the back of the Cathode Ray tube)
> 
> Using an ohmmeter, you can determine which wire is the other side of the 
> HT coil, and which wires are the low-voltage coil (they'll have less 
> resistance, and maybe even a centre-tap point)

Um... this sounds a little disturbing...

> Fashion up a convenient 555 timer circuit on a 12-volt plugpack.  Tune 
> it to about 16 kHz.  (or just go for "high squeal like a TV" set).  
> Buffer its output with either a single-ended, or for more efficiency, a 
> push-pull power transistor output stage.  A naked 2N3055 will do fine, 
> but you can use a smaller power transistor if you bolt it onto a 
> heatsink.  Remember to put reverse-biased power diodes across the output 
> transistor to soak up the back-EMF from the primary coil or you'll 
> probably fritz your transistor pretty quick.
> 
> Eg. Assuming you have an NPN power transistor with emitter to Ground, 
> bung its collector in series with the low-Volt primary winding to the 12 
> Volt rail.  Now, you need...

...I have no idea what you just said...

> One clear 240-Volt tungsten incandescent bulb, but with a popped 
> filament. It needs to have enough filament intact that there isn't too 
> big a gap.
> 
> Hook the bulb up to the HT side of the transformer, turn the whole 
> kaboodle on, and with a little luck, the bulb will display a lovely 
> pinkish-violet ionised argon "flame" between the filament ends.  It'll 
> should have enough energy to make the filament red hot and the glass hot 
> above the convective "flame".

Erm... I think I'll just stick with my plasma ball at home. ;-)

[EDIT: Just as soon as I can find the damn power supply...!]

Did you know, if you balance a metal object on the glass, and hold your 
finger just the right distance from it, it produces a continues bright 
blue spark? However, be careful; I actually burnt my finger this way...


Post a reply to this message

From: Ross
Subject: Re: Wahahahaha!
Date: 9 Nov 2007 12:14:21
Message: <4734956d@news.povray.org>
"Paul Fuller" <pgf### [at] optusnetcomau> wrote in message
news:472c590d@news.povray.org...
> Orchid XP v7 wrote:
> > Are YOU man enough to turn up to the office on Monday sporting one of
> > these? 0;-)
> >
> > ------------------------------------------------------------------------
> >
> Let me know when you have a model that animates a fractal zoom.  Or at
> least one that performs colour cycling ala FractInt when you press a
button.
>
> At work we used to occasionally have 'Horrible Tie and Ugly Sock Day' -
> with prizes for the worst in each category.  While fractals can be
> beautiful I think any one of these would have won the tie category
> easily. :)

LOL. I want fractal socks now :)

honestly i think the ties are kinda cool. total nerd factor... WIN!


Post a reply to this message

From: Jim Henderson
Subject: Re: Wahahahaha!
Date: 9 Nov 2007 15:50:04
Message: <4734c7fc@news.povray.org>
On Fri, 09 Nov 2007 09:34:25 +0000, Invisible wrote:

> Jim Henderson wrote:
>> On Thu, 08 Nov 2007 18:20:39 +0000, Orchid XP v7 wrote:
>> 
>>> Nicolas Alvarez wrote:
>>>> Invisible escribió:
>>>>> (I never really understood why programs produce core dumps. I mean,
>>>>> seriously. What chance is there of anybody *ever* deducing anything
>>>>> useful from this data? 10^-78?)
>>>> The original programmer with access to the sourcecode *can* deduce
>>>> data from it.
>>> I seriously doubt it...
>> 
>> I've done it, several times, even with things I'm not the original
>> programmer for but have access to the source code.
> 
> Really?

Yes, really. :-)

> Well, it still sounds absurdly improbable to me, but I'll take your word
> for it.

Part of the contents of a program in memory is a symbol table - which is 
a table that basically tells you what data is stored where.  After all, 
the program has to know where the value for a variable called "a" is 
stored, which means that can be figured out.  You don't need a full 
system core for this (which used to be the way it was done, in fact, with 
my experience working with NetWare, that *was* the way it was done - the 
entire contents of memory were dumped along with the current state of the 
system).  EIP tells you where the program is currently executing and the 
various registers tell you the state of the machine - such as if there's 
an overflow, PFPE, or some other sort of issue that caused the crash.

So what you do, working at a machine level, is start with where EIP is 
and work backwards.  You look at the stack backtrace to see what 
functions called what functions, and you can figure out what code path 
the program had taken.

It's a hell of a lot easier if you have symbolic debug information 
available to you, but it's not impossible if you don't - just takes a bit 
more time to diagnose.  Sometimes a *lot* more time.

From a code standpoint, using Borland C++ (years ago), there was a source-
level debugger that you could single step through.  IIRC, there was a way 
to take data from a crashed program and use it as well, but it's been a 
long time since I did that.

At the moment, the only core file on my system is from novfsd (the Novell 
Client for Linux daemon), which I don't have symbol info for, but even 
loading the core up in gdb, I can tell that it suffered a segmentation 
fault.  With a symbol table, it could pinpoint exactly where the daemon 
crashed and from there the developers could code a fix for it.  As it is, 
the backtrace tells me what values are on the stack, but not the name of 
the symbol at the address.  But that's what the --symbols parameter is 
for - to tell it to read in the symbol table.

> Now, how about that Windoze habit of saying "The program has experienced
> an error and will be shut down. Do you want to send debugging
> information?" What do you estimate the chances are that *anybody* will
> do anything at all with the data thus sent? ;-)

Knowing some of the people who do the analysis on that type of data, I'd 
say fairly good, actually.  It starts with statistical analysis of the 
reports coming in, and the things that happen most frequently are likely 
candidates for a fix to be written.  Of course, different vendors do this 
different ways.

I watched one engineer do live debugging of a client issue on a Windows 
system; watching someone use a tool like that who knows what they're 
doing is a very interesting thing, because they can pull information 
about what's going on at any given point in the process.  Doing it live 
or doing it from a core file is pretty similar, except that with a core 
file the system isn't changing; it's actually the *easier* way to debug, 
because you're working from a snapshot of a program at a point in time 
instead of watching things change.

It's not much different, procedurally, than what CSIs go through in 
trying to reconstruct a crime scene.  They arrive and things have already 
happened, and they have to piece together what transpired ahead of time 
in order to build a case.  (Of course CSI is more difficult because 
people don't act logically; computers do, and as such, they're quite a 
bit more predictable).

Though arguably watching things change on a live system can provide more 
insight into how you got to a point.

Jim


Post a reply to this message

From: Orchid XP v7
Subject: Re: Wahahahaha!
Date: 9 Nov 2007 16:02:31
Message: <4734cae7$1@news.povray.org>
Jim Henderson wrote:

> Part of the contents of a program in memory is a symbol table - which is 
> a table that basically tells you what data is stored where.  After all, 
> the program has to know where the value for a variable called "a" is 
> stored, which means that can be figured out.

Now, see, I was told the purpose of a "linker" is to elide all such data 
before building the final executable. ;-)

> So what you do, working at a machine level, is start with where EIP is 
> and work backwards.  You look at the stack backtrace to see what 
> functions called what functions, and you can figure out what code path 
> the program had taken.

Yeah, but let's be real here. The actual generated machine code is going 
to bear *no relationship* to the original program source code. Only a 
super-hyper-nerd is ever going to get anything useful out of it.

> From a code standpoint, using Borland C++ (years ago), there was a source-
> level debugger that you could single step through.  IIRC, there was a way 
> to take data from a crashed program and use it as well, but it's been a 
> long time since I did that.

That's impressive. Usually these things work by inserting software 
interrupts into the code. (Or just software enumation of machine state...)


Post a reply to this message

From: Nicolas Alvarez
Subject: Re: Wahahahaha!
Date: 9 Nov 2007 17:22:08
Message: <4734dd90$1@news.povray.org>
Orchid XP v7 escribió:
>> So what you do, working at a machine level, is start with where EIP is 
>> and work backwards.  You look at the stack backtrace to see what 
>> functions called what functions, and you can figure out what code path 
>> the program had taken.
> 
> Yeah, but let's be real here. The actual generated machine code is going 
> to bear *no relationship* to the original program source code. Only a 
> super-hyper-nerd is ever going to get anything useful out of it.
> 

That's what the debugging symbols can do too. Mapping between lines of 
code and instruction addresses.

Note that it's usually a lot harder on optimized executables. 
Single-stepping on a running program that has been optimized is almost 
impossible. It appears to run instructions twice, run instructions in 
strange order, etc. So disabling optimizations for stepping through a 
program is highly recommended...


Post a reply to this message

From: Jim Henderson
Subject: Re: Wahahahaha!
Date: 9 Nov 2007 17:46:14
Message: <4734e336$1@news.povray.org>
On Fri, 09 Nov 2007 21:02:39 +0000, Orchid XP v7 wrote:

> Jim Henderson wrote:
> 
>> Part of the contents of a program in memory is a symbol table - which
>> is a table that basically tells you what data is stored where.  After
>> all, the program has to know where the value for a variable called "a"
>> is stored, which means that can be figured out.
> 
> Now, see, I was told the purpose of a "linker" is to elide all such data
> before building the final executable. ;-)

No, the final executable *needs* to know this.  You may lose the variable 
name, but the pointer from the variable itself to a memory location is 
something the program *must* know.

>> So what you do, working at a machine level, is start with where EIP is
>> and work backwards.  You look at the stack backtrace to see what
>> functions called what functions, and you can figure out what code path
>> the program had taken.
> 
> Yeah, but let's be real here. The actual generated machine code is going
> to bear *no relationship* to the original program source code. Only a
> super-hyper-nerd is ever going to get anything useful out of it.

Actually, I am being real - it doesn't take a super-hyper-nerd to do what 
I'm describing.  It requires a bit of a background in software 
development and coding and knowledge of how the systems actually work.

Software engineers do this sort of thing every day - it's part of the job 
description.

>> From a code standpoint, using Borland C++ (years ago), there was a
>> source- level debugger that you could single step through.  IIRC, there
>> was a way to take data from a crashed program and use it as well, but
>> it's been a long time since I did that.
> 
> That's impressive. Usually these things work by inserting software
> interrupts into the code. (Or just software enumation of machine
> state...)

Technically it is impressive to be able to do that (especially if you've 
never seen it done before) - but the tools make it very very easy to do.  
I've taken cores and pulled stack traces and variables data out of them 
and compared to stacks in source code using tools like Source Navigator, 
which can give you detailed information about various functions including 
a way of looking at the call stacks so you can see what's going on as you 
step through the program.  Very easy to use, and very useful for this 
type of debugging.

I took a crash file from a system and combined with the use of SN, I was 
able to pinpoint *exactly* what changed in the code that caused the crash 
(comparing old version to new version) and submitted a patch.  Turned out 
the engineer had fixed it the day prior to my analysis, but my proposed 
fix was what he did to fix it.  That I came to the same conclusion using 
these tools as the guy who originally wrote the code should tell you 
something about the feasibility of using tools like this to accomplish 
this sort of task.  It all started with a core file.

Jim


Post a reply to this message

From: Jim Henderson
Subject: Re: Wahahahaha!
Date: 9 Nov 2007 17:47:29
Message: <4734e381$1@news.povray.org>
On Fri, 09 Nov 2007 19:22:02 -0300, Nicolas Alvarez wrote:

> Note that it's usually a lot harder on optimized executables.

Depends on whether the debugger in use is aware of how the optimizations 
work; but yes, I believe in Turbo C and BC++, using the inline debugger 
did generate non-optimized code in order for the single-step operations 
to work.

Jim


Post a reply to this message

From: Alain
Subject: Re: Wahahahaha!
Date: 9 Nov 2007 18:36:59
Message: <4734ef1b@news.povray.org>
Stephen nous apporta ses lumieres en ce 2007/11/08 03:31:
> Alain <ele### [at] netscapenet> wrote:
>> Stephen nous apporta ses lumieres en ce 2007/11/07 03:00:
> 
>>> You always could recharge non-rechargeable batteries. The manufacturers do
>>> notlike it though.
>>>
>>> Stephen
>>>
>>>
>>>
>> You can, but they don't keep the charge very well. The ones I did recharge
>> lasted less than half as long as rechargeable ones. They also got warmer during
>> the recharge.
>>
> 
> 
> They do get warm but I think that it depends on the charger and the current it
> uses for charging. Don’t say it! That was a stupid thing to say. Of course it
> depends on the current. I built mine myself and charged them at about 20 ma and
> IIRC discharge was between 7.5 and 10 ma.
> If your batteries are not holding their charge then the discharge cycle is
> probably too low.
> And that came from another life, one before Pov :)
> Also if you were old enough to wire up a mains plug you were old enough to die.
> Dear oh dear the things that didn’t kill us. :) I wouldn’t like to put in
> writing some of the things that I did.
> 
> 
> Stephen
> 
> 
Not a main plug. The whire of a lamp had to be replaced. My father kept the plug 
and the intact part of the whire, about 1'. I found it. I hooked the speaker to 
it, and wrapt with masking tape. Used that to plug the speaker in the wall. 120 
volts for a speaker made for a small radio that used a 9V batery...

-- 
Alain
-------------------------------------------------
You know you've been raytracing too long when you look at waterfalls, dust, 
rain, snow, etc, and think: "If only I had a fractalized, vector based 
particle-system modeler with collision detection!"


Post a reply to this message

From: Alain
Subject: Re: Wahahahaha!
Date: 9 Nov 2007 18:59:53
Message: <4734f479$1@news.povray.org>
Jim Henderson nous apporta ses lumieres en ce 2007/11/09 15:50:
> On Fri, 09 Nov 2007 09:34:25 +0000, Invisible wrote:
> 
>> Jim Henderson wrote:
>>> On Thu, 08 Nov 2007 18:20:39 +0000, Orchid XP v7 wrote:
>>>
>>>> Nicolas Alvarez wrote:
>>>>> Invisible escribió:
>>>>>> (I never really understood why programs produce core dumps. I mean,
>>>>>> seriously. What chance is there of anybody *ever* deducing anything
>>>>>> useful from this data? 10^-78?)
>>>>> The original programmer with access to the sourcecode *can* deduce
>>>>> data from it.
>>>> I seriously doubt it...
>>> I've done it, several times, even with things I'm not the original
>>> programmer for but have access to the source code.
>> Really?
> 
> Yes, really. :-)
> 
>> Well, it still sounds absurdly improbable to me, but I'll take your word
>> for it.
> 
> Part of the contents of a program in memory is a symbol table - which is 
> a table that basically tells you what data is stored where.  After all, 
> the program has to know where the value for a variable called "a" is 
> stored, which means that can be figured out.  You don't need a full 
> system core for this (which used to be the way it was done, in fact, with 
> my experience working with NetWare, that *was* the way it was done - the 
> entire contents of memory were dumped along with the current state of the 
> system).  EIP tells you where the program is currently executing and the 
> various registers tell you the state of the machine - such as if there's 
> an overflow, PFPE, or some other sort of issue that caused the crash.
> 
> So what you do, working at a machine level, is start with where EIP is 
> and work backwards.  You look at the stack backtrace to see what 
> functions called what functions, and you can figure out what code path 
> the program had taken.
There are times when you can't do a stack backtrace because the stack have been 
corrupted. Something like a bad vector that send you to a bit of code that call 
a subprocess, pushing the return address on the stack, and the code pointed to 
ask tou to jump the another subprocess, whitch is itself. Infinite loop causing 
a stack overflow, and in some cases, the stack cycling pointer cycling back to zero.
Or you enter a loop that pop data out of the stack until there is no more data 
to retreive, and the stack pointer jump to the largest value it can contain.
There are times when the crash can cause corruption far outside the area that a 
process is allowed to access.

> 
> It's a hell of a lot easier if you have symbolic debug information 
> available to you, but it's not impossible if you don't - just takes a bit 
> more time to diagnose.  Sometimes a *lot* more time.
True.
> 
> From a code standpoint, using Borland C++ (years ago), there was a source-
> level debugger that you could single step through.  IIRC, there was a way 
> to take data from a crashed program and use it as well, but it's been a 
> long time since I did that.
> 
> At the moment, the only core file on my system is from novfsd (the Novell 
> Client for Linux daemon), which I don't have symbol info for, but even 
> loading the core up in gdb, I can tell that it suffered a segmentation 
> fault.  With a symbol table, it could pinpoint exactly where the daemon 
> crashed and from there the developers could code a fix for it.  As it is, 
> the backtrace tells me what values are on the stack, but not the name of 
> the symbol at the address.  But that's what the --symbols parameter is 
> for - to tell it to read in the symbol table.
> 
>> Now, how about that Windoze habit of saying "The program has experienced
>> an error and will be shut down. Do you want to send debugging
>> information?" What do you estimate the chances are that *anybody* will
>> do anything at all with the data thus sent? ;-)
> 
> Knowing some of the people who do the analysis on that type of data, I'd 
> say fairly good, actually.  It starts with statistical analysis of the 
> reports coming in, and the things that happen most frequently are likely 
> candidates for a fix to be written.  Of course, different vendors do this 
> different ways.
> 
> I watched one engineer do live debugging of a client issue on a Windows 
> system; watching someone use a tool like that who knows what they're 
> doing is a very interesting thing, because they can pull information 
> about what's going on at any given point in the process.  Doing it live 
> or doing it from a core file is pretty similar, except that with a core 
> file the system isn't changing; it's actually the *easier* way to debug, 
> because you're working from a snapshot of a program at a point in time 
> instead of watching things change.
Easier to look at a snapshot than to the changes. The snapshot is frozen. If you 
try to look as it changes, it's usualy to fast.
> 
> It's not much different, procedurally, than what CSIs go through in 
> trying to reconstruct a crime scene.  They arrive and things have already 
> happened, and they have to piece together what transpired ahead of time 
> in order to build a case.  (Of course CSI is more difficult because 
> people don't act logically; computers do, and as such, they're quite a 
> bit more predictable).
> 
> Though arguably watching things change on a live system can provide more 
> insight into how you got to a point.
> 
> Jim


-- 
Alain
-------------------------------------------------
Lutheran: If shit happens, don't talk about it.


Post a reply to this message

From: Alain
Subject: Re: Wahahahaha!
Date: 9 Nov 2007 19:14:14
Message: <4734f7d6@news.povray.org>
Invisible nous apporta ses lumieres en ce 2007/11/08 04:34:
> ...I'm beginning to think POV-Ray attracts crazy people... o_O
Not at all! Just peoples that are more curious than the norm ;) thus, good 
learners and thinkerers. Probably, also, who have an IQ higher than average.

-- 
Alain
-------------------------------------------------
Tricks and treachery are the practice of fools, that don't have brains enough to 
be honest.
Benjamin Franklin


Post a reply to this message

From: Jim Henderson
Subject: Re: Wahahahaha!
Date: 10 Nov 2007 17:34:52
Message: <4736320c@news.povray.org>
On Fri, 09 Nov 2007 18:59:50 -0500, Alain wrote:


> There are times when you can't do a stack backtrace because the stack
> have been corrupted. Something like a bad vector that send you to a bit
> of code that call a subprocess, pushing the return address on the stack,
> and the code pointed to ask tou to jump the another subprocess, whitch
> is itself. Infinite loop causing a stack overflow, and in some cases,
> the stack cycling pointer cycling back to zero. Or you enter a loop that
> pop data out of the stack until there is no more data to retreive, and
> the stack pointer jump to the largest value it can contain. There are
> times when the crash can cause corruption far outside the area that a
> process is allowed to access.

Absolutely this can happen.  In my experience, it's not terribly common, 
but sure, ESP and EBP can contain invalid values which can make it ugly 
or impossible to diagnose.  These situations are the exception (pun not 
intended) rather than the rule.

>> I watched one engineer do live debugging of a client issue on a Windows
>> system; watching someone use a tool like that who knows what they're
>> doing is a very interesting thing, because they can pull information
>> about what's going on at any given point in the process.  Doing it live
>> or doing it from a core file is pretty similar, except that with a core
>> file the system isn't changing; it's actually the *easier* way to
>> debug, because you're working from a snapshot of a program at a point
>> in time instead of watching things change.
> Easier to look at a snapshot than to the changes. The snapshot is
> frozen. If you try to look as it changes, it's usualy to fast.

Yes, a snapshot is easier.  Fortunately, if you're doing "live" 
debugging, you do have the opportunity to halt things and look at the 
state, and then single step over or through functions.  That doesn't help 
if the issue is a timing issue, but those can be the most difficult to 
nail down.

Having access at the kernel level, you can do all kinds of neat things.

Jim


Post a reply to this message

From: Darren New
Subject: Re: Wahahahaha!
Date: 11 Nov 2007 17:34:50
Message: <4737838a@news.povray.org>
Invisible wrote:
> Now, how about that Windoze habit of saying "The program has experienced 
> an error and will be shut down. Do you want to send debugging 
> information?" What do you estimate the chances are that *anybody* will 
> do anything at all with the data thus sent? ;-)

I have, on occasion, sent in reports like that, and had Microsoft reply 
with how to fix it. So obviously someone was paying attention to it.

-- 
   Darren New / San Diego, CA, USA (PST)
     Remember the good old days, when we
     used to complain about cryptography
     being export-restricted?


Post a reply to this message

From: Darren New
Subject: Re: Wahahahaha!
Date: 11 Nov 2007 17:36:46
Message: <473783fe$1@news.povray.org>
Orchid XP v7 wrote:
> That's impressive. Usually these things work by inserting software 
> interrupts into the code. (Or just software enumation of machine state...)

Nowadays, actually, they tend to play with the memory map to cause traps 
to occur where you want to see things. Breakpoint when you write a 
variable? Map the page the variable is in as read-only, then when the 
trap happens, see if the instruction was pointing to the variable.

-- 
   Darren New / San Diego, CA, USA (PST)
     Remember the good old days, when we
     used to complain about cryptography
     being export-restricted?


Post a reply to this message

From: Darren New
Subject: Re: Wahahahaha!
Date: 11 Nov 2007 17:40:46
Message: <473784ee$1@news.povray.org>
Warp wrote:
> Darren New <dne### [at] sanrrcom> wrote:
>> Most other languages don't futz with the class of the object while it's 
>> being constructed, so it doesn't really come up, I guess. One of the 
>> costs of multiple inheritance as implemented by C++?
> 
>   I don't understand what multiple inheritance has to do with this.

The need for multiple vtables in the final class.  Well, it's not 
specifically multiple inheritance, but rather the fact that vtables are 
indexed with fixed indecies for virtual functions, which means you have 
to modify the base pointer if you have more than one parent class.

If you only have one chain of inheritance, then the virtual functions in 
child classes can always come after the virtual functions in parent 
classes without conflict. If you have multiple inheritance, two parent 
classes might assign the same index to two different virtual functions, 
and something that inherits from both needs to disambiguate.

-- 
   Darren New / San Diego, CA, USA (PST)
     Remember the good old days, when we
     used to complain about cryptography
     being export-restricted?


Post a reply to this message

From: Darren New
Subject: Re: Wahahahaha!
Date: 11 Nov 2007 17:41:56
Message: <47378534$1@news.povray.org>
Warp wrote:
>   It would be difficult for the compiler to follow how the functions are
> being called (and, in fact, it's impossible for it to know if the pure
> virtual function actually gets called in the general case).

Especially if that function is already compiled and in a library 
somewhere. :-)

>   The problem with calling a pure virtual function in the base class
> constructor is that the derived class has yet not been initialized and
> thus calling a derived class function implementation could cause undefined
> behavior because it's not constructed.

You mean, undefined behavior as opposed to a core dump? ;-)

-- 
   Darren New / San Diego, CA, USA (PST)
     Remember the good old days, when we
     used to complain about cryptography
     being export-restricted?


Post a reply to this message

From: Warp
Subject: Re: Wahahahaha!
Date: 11 Nov 2007 18:06:46
Message: <47378b06@news.povray.org>
Darren New <dne### [at] sanrrcom> wrote:
> >   The problem with calling a pure virtual function in the base class
> > constructor is that the derived class has yet not been initialized and
> > thus calling a derived class function implementation could cause undefined
> > behavior because it's not constructed.

> You mean, undefined behavior as opposed to a core dump? ;-)

  Yes, undefined behavior. It could work like a charm, or it could cause
a segmentation fault. (The latter may easily happen if, for example, the
function in the derived class accesses eg. a string, which obviously has
not yet been initialized and contains garbage.)

-- 
                                                          - Warp


Post a reply to this message

From: Invisible
Subject: Re: Wahahahaha!
Date: 12 Nov 2007 04:25:54
Message: <47381c22$1@news.povray.org>
Alain wrote:
> Invisible nous apporta ses lumieres en ce 2007/11/08 04:34:
>> ...I'm beginning to think POV-Ray attracts crazy people... o_O
> Not at all! Just peoples that are more curious than the norm ;) thus, 
> good learners and thinkerers. Probably, also, who have an IQ higher than 
> average.

Well, maybe you guys do. Mine is only 103... :-(


Post a reply to this message

From: andrel
Subject: Re: Wahahahaha!
Date: 12 Nov 2007 04:35:07
Message: <47381F56.9060401@hotmail.com>
Invisible wrote:
> Alain wrote:
>> Invisible nous apporta ses lumieres en ce 2007/11/08 04:34:
>>> ...I'm beginning to think POV-Ray attracts crazy people... o_O
>> Not at all! Just peoples that are more curious than the norm ;) thus, 
>> good learners and thinkerers. Probably, also, who have an IQ higher 
>> than average.
> 
> Well, maybe you guys do. Mine is only 103... :-(
The average is 100 by definition. So, what are you trying to prove? 
Perhaps that your math skills have declined since taking that test and 
that you should be below 100 now? Some complicated sort of self 
fulfilling estimate?


Post a reply to this message

From: Orchid XP v7
Subject: Re: Wahahahaha!
Date: 12 Nov 2007 14:09:26
Message: <4738a4e6$1@news.povray.org>
Darren New wrote:
> Orchid XP v7 wrote:
>> That's impressive. Usually these things work by inserting software 
>> interrupts into the code. (Or just software enumation of machine 
>> state...)
> 
> Nowadays, actually, they tend to play with the memory map to cause traps 
> to occur where you want to see things. Breakpoint when you write a 
> variable? Map the page the variable is in as read-only, then when the 
> trap happens, see if the instruction was pointing to the variable.

Interesting. I thought (in C) all variables exist on the machine stack?


Post a reply to this message

From: Orchid XP v7
Subject: Re: Wahahahaha!
Date: 12 Nov 2007 14:10:07
Message: <4738a50f$1@news.povray.org>
Darren New wrote:
> Invisible wrote:
>> Now, how about that Windoze habit of saying "The program has 
>> experienced an error and will be shut down. Do you want to send 
>> debugging information?" What do you estimate the chances are that 
>> *anybody* will do anything at all with the data thus sent? ;-)
> 
> I have, on occasion, sent in reports like that, and had Microsoft reply 
> with how to fix it. So obviously someone was paying attention to it.

Woah. Micro$oft talking to a paying customer... that's almost unheard 
of. o_O

You must be very special...


Post a reply to this message

From: Fredrik Eriksson
Subject: Re: Wahahahaha!
Date: 12 Nov 2007 14:40:17
Message: <op.t1o19egccs6ysw@e6600>
On Mon, 12 Nov 2007 20:09:27 +0100, Orchid XP v7 <voi### [at] devnull> wrote:
> Darren New wrote:
>> Orchid XP v7 wrote:
>>> That's impressive. Usually these things work by inserting software  
>>> interrupts into the code. (Or just software enumation of machine  
>>> state...)
>>  Nowadays, actually, they tend to play with the memory map to cause  
>> traps to occur where you want to see things. Breakpoint when you write  
>> a variable? Map the page the variable is in as read-only, then when the  
>> trap happens, see if the instruction was pointing to the variable.
>
> Interesting. I thought (in C) all variables exist on the machine stack?

Not true, but even so, the stack is still memory.


-- 
FE


Post a reply to this message

From: Orchid XP v7
Subject: Re: Wahahahaha!
Date: 12 Nov 2007 15:22:17
Message: <4738b5f9@news.povray.org>
Fredrik Eriksson wrote:

>>>  Nowadays, actually, they tend to play with the memory map to cause 
>>> traps to occur where you want to see things. Breakpoint when you 
>>> write a variable? Map the page the variable is in as read-only, then 
>>> when the trap happens, see if the instruction was pointing to the 
>>> variable.
>>
>> Interesting. I thought (in C) all variables exist on the machine stack?
> 
> Not true, but even so, the stack is still memory.

Well true - but my point was more that the stack gets touched every 3 
instructions or so, and setting traps on it would light up the system 
like a festive season tree. ;-)


Post a reply to this message

From: Alain
Subject: Re: Wahahahaha!
Date: 12 Nov 2007 18:45:23
Message: <4738e593$1@news.povray.org>
Invisible nous apporta ses lumieres en ce 2007/11/12 04:25:
> Alain wrote:
>> Invisible nous apporta ses lumieres en ce 2007/11/08 04:34:
>>> ...I'm beginning to think POV-Ray attracts crazy people... o_O
>> Not at all! Just peoples that are more curious than the norm ;) thus, 
>> good learners and thinkerers. Probably, also, who have an IQ higher 
>> than average.
> 
> Well, maybe you guys do. Mine is only 103... :-(
It's above average ;)
An IQ of 100 is average by definition. Anything >100 is above average.

-- 
Alain
-------------------------------------------------
A Bill of Rights is what the people are entitled to against every
government, and what no just government should refuse, or rest on inference.
Thomas Jefferson


Post a reply to this message

From: Nicolas Alvarez
Subject: Re: Wahahahaha!
Date: 12 Nov 2007 19:02:33
Message: <4738e999$1@news.povray.org>
Orchid XP v7 escribió:
> 
> Woah. Micro$oft talking to a paying customer... that's almost unheard 
> of. o_O
> 
> You must be very special...

Or paying more.


Post a reply to this message

From: Darren New
Subject: Re: Wahahahaha!
Date: 12 Nov 2007 23:34:10
Message: <47392942$1@news.povray.org>
Orchid XP v7 wrote:
>> Nowadays, actually, they tend to play with the memory map to cause 
>> traps to occur where you want to see things. Breakpoint when you write 
>> a variable? Map the page the variable is in as read-only, then when 
>> the trap happens, see if the instruction was pointing to the variable.
> 
> Interesting. I thought (in C) all variables exist on the machine stack?

Dunno. Often, the static variables (i.e., those with a lifetime that 
matches the process) are allocated, well, statically. Whether it's part 
of the stack that never gets popped or not isn't too relevant.

Anyway, so? The machine stack is in memory-mapped memory too, yes?

-- 
   Darren New / San Diego, CA, USA (PST)
     Remember the good old days, when we
     used to complain about cryptography
     being export-restricted?


Post a reply to this message

From: Darren New
Subject: Re: Wahahahaha!
Date: 12 Nov 2007 23:34:32
Message: <47392958$1@news.povray.org>
Orchid XP v7 wrote:
> Well true - but my point was more that the stack gets touched every 3 
> instructions or so, and setting traps on it would light up the system 
> like a festive season tree. ;-)

Nobody said it was an *efficient* way to do it.

-- 
   Darren New / San Diego, CA, USA (PST)
     Remember the good old days, when we
     used to complain about cryptography
     being export-restricted?


Post a reply to this message

From: Darren New
Subject: Re: Wahahahaha!
Date: 12 Nov 2007 23:35:13
Message: <47392981@news.povray.org>
Orchid XP v7 wrote:
> Darren New wrote:
>> Invisible wrote:
>>> Now, how about that Windoze habit of saying "The program has 
>>> experienced an error and will be shut down. Do you want to send 
>>> debugging information?" What do you estimate the chances are that 
>>> *anybody* will do anything at all with the data thus sent? ;-)
>>
>> I have, on occasion, sent in reports like that, and had Microsoft 
>> reply with how to fix it. So obviously someone was paying attention to 
>> it.
> 
> Woah. Micro$oft talking to a paying customer... that's almost unheard 
> of. o_O
> 
> You must be very special...

Um, no. It looks up the problem in the database and points you to the KB 
article. Automated.

-- 
   Darren New / San Diego, CA, USA (PST)
     Remember the good old days, when we
     used to complain about cryptography
     being export-restricted?


Post a reply to this message

From: Invisible
Subject: Re: Wahahahaha!
Date: 13 Nov 2007 04:31:10
Message: <47396ede$1@news.povray.org>
>> Interesting. I thought (in C) all variables exist on the machine stack?
> 
> Dunno. Often, the static variables (i.e., those with a lifetime that 
> matches the process) are allocated, well, statically. Whether it's part 
> of the stack that never gets popped or not isn't too relevant.

When it comes to watching the CPU twiddle individual bits, *everything* 
becomes relevant. (That's why it's such an inefficient way to debug 
things...)

> Anyway, so? The machine stack is in memory-mapped memory too, yes?

Usually. ;-) (I understand there are designs where it isn't. Not that it 
matters too much...)


Post a reply to this message

From: Invisible
Subject: Re: Wahahahaha!
Date: 13 Nov 2007 04:35:48
Message: <47396ff4$1@news.povray.org>
Alain wrote:
> Invisible nous apporta ses lumieres en ce 2007/11/12 04:25:
>> Alain wrote:
>>> Invisible nous apporta ses lumieres en ce 2007/11/08 04:34:
>>>> ...I'm beginning to think POV-Ray attracts crazy people... o_O
>>> Not at all! Just peoples that are more curious than the norm ;) thus, 
>>> good learners and thinkerers. Probably, also, who have an IQ higher 
>>> than average.
>>
>> Well, maybe you guys do. Mine is only 103... :-(
> It's above average ;)
> An IQ of 100 is average by definition. Anything >100 is above average.

I guess the critical question is the SD...


Post a reply to this message

From: Stephen
Subject: Re: Wahahahaha!
Date: 13 Nov 2007 07:15:01
Message: <web.473995156f9d6136c4e49fa40@news.povray.org>
Invisible <voi### [at] devnull> wrote:
> Alain wrote:
> > Invisible nous apporta ses lumieres en ce 2007/11/12 04:25:
> >> Alain wrote:
> >>> Invisible nous apporta ses lumieres en ce 2007/11/08 04:34:
> >>>> ...I'm beginning to think POV-Ray attracts crazy people... o_O
> >>> Not at all! Just peoples that are more curious than the norm ;) thus,
> >>> good learners and thinkerers. Probably, also, who have an IQ higher
> >>> than average.
> >>
> >> Well, maybe you guys do. Mine is only 103... :-(
> > It's above average ;)
> > An IQ of 100 is average by definition. Anything >100 is above average.
>
> I guess the critical question is the SD...


The critical question is, “What is IQ and why so people believe it can be of
use?”

IMO

Stephen


Post a reply to this message

From: Phil Cook
Subject: Re: Wahahahaha!
Date: 13 Nov 2007 07:59:08
Message: <op.t1qebpf2c3xi7v@news.povray.org>
And lo on Tue, 13 Nov 2007 12:14:13 -0000, Stephen <mcavoys_AT_aolDOT.com>  
did spake, saying:

> Invisible <voi### [at] devnull> wrote:
>> Alain wrote:
>> > Invisible nous apporta ses lumieres en ce 2007/11/12 04:25:
>> >> Alain wrote:
>> >>> Invisible nous apporta ses lumieres en ce 2007/11/08 04:34:
>> >>>> ...I'm beginning to think POV-Ray attracts crazy people... o_O
>> >>> Not at all! Just peoples that are more curious than the norm ;)  
>> thus,
>> >>> good learners and thinkerers. Probably, also, who have an IQ higher
>> >>> than average.
>> >>
>> >> Well, maybe you guys do. Mine is only 103... :-(
>> > It's above average ;)
>> > An IQ of 100 is average by definition. Anything >100 is above average.
>>
>> I guess the critical question is the SD...
>
>
> The critical question is, “What is IQ and why so people believe it can  
> be of use?”

Because it allows people to measure something unmeasurable then compare it  
to other people's results.

-- 
Phil Cook

--
I once tried to be apathetic, but I just couldn't be bothered
http://flipc.blogspot.com


Post a reply to this message

From: Invisible
Subject: Re: Wahahahaha!
Date: 13 Nov 2007 08:24:32
Message: <4739a590@news.povray.org>
Stephen wrote:

> The critical question is, “What is IQ and why so people believe it can be of
> use?”

Well, it is self-evident that some people are much more intelligent than 
others. IQ is one attempt to measure this in some kind of objective way 
(with varying degrees of success).


Post a reply to this message

From: scott
Subject: Re: Wahahahaha!
Date: 13 Nov 2007 08:43:11
Message: <4739a9ef$1@news.povray.org>
>> I have, on occasion, sent in reports like that, and had Microsoft reply 
>> with how to fix it. So obviously someone was paying attention to it.
>
> Woah. Micro$oft talking to a paying customer... that's almost unheard of. 
> o_O
>
> You must be very special...

Go to microsoft.co.uk and click on Support, then Help & Support home, 
Contact Us then "contact a support professional by phone or email".  I used 
it once at work because of some insane issue with Visual C++ .net, I was 
prepared to pay for the call, but as it turned out to be a bug they didn't 
charge me and sent me a pre-release update so I could work around the 
problem :-)


Post a reply to this message

From: Phil Cook
Subject: Re: Wahahahaha!
Date: 13 Nov 2007 09:32:19
Message: <op.t1qimm0mc3xi7v@news.povray.org>
And lo on Tue, 13 Nov 2007 13:24:31 -0000, Invisible <voi### [at] devnull> did  
spake, saying:

> Stephen wrote:
>
>> The critical question is, “What is IQ and why so people believe it can  
>> be of
>> use?”
>
> Well, it is self-evident that some people are much more intelligent than  
> others.

While it is self-evident that some people are more intelligent than  
others, it is also self-evident that some people are dumber then others;  
what is not commonly understood is that these facts often involves the  
same people merely at different times and in different situations.

> IQ is one attempt to measure this in some kind of objective way (with  
> varying degrees of success).

Although that simply shifts the question to the next level of "So why are  
bothering to measure this?"

-- 
Phil Cook

--
I once tried to be apathetic, but I just couldn't be bothered
http://flipc.blogspot.com


Post a reply to this message

From: Invisible
Subject: Re: Wahahahaha!
Date: 13 Nov 2007 09:59:36
Message: <4739bbd8$1@news.povray.org>
Phil Cook wrote:

> While it is self-evident that some people are more intelligent than 
> others, it is also self-evident that some people are dumber then others; 
> what is not commonly understood is that these facts often involves the 
> same people merely at different times and in different situations.

Well, the guys at XKCD know about it at least:

http://www.xkcd.com/231/

>> IQ is one attempt to measure this in some kind of objective way (with 
>> varying degrees of success).
> 
> Although that simply shifts the question to the next level of "So why 
> are bothering to measure this?"

Well, if you're going to put it that way... why are we bothering to be 
live? It's not like there's any point to it...


Post a reply to this message

From: Phil Cook
Subject: Re: Wahahahaha!
Date: 13 Nov 2007 10:26:11
Message: <op.t1qk38f8c3xi7v@news.povray.org>
And lo on Tue, 13 Nov 2007 14:59:35 -0000, Invisible <voi### [at] devnull> did  
spake, saying:

> Phil Cook wrote:
>
>> While it is self-evident that some people are more intelligent than  
>> others, it is also self-evident that some people are dumber then  
>> others; what is not commonly understood is that these facts often  
>> involves the same people merely at different times and in different  
>> situations.
>
> Well, the guys at XKCD know about it at least:
>
> http://www.xkcd.com/231/

Indeed

>>> IQ is one attempt to measure this in some kind of objective way (with  
>>> varying degrees of success).
>>  Although that simply shifts the question to the next level of "So why  
>> are bothering to measure this?"
>
> Well, if you're going to put it that way... why are we bothering to be  
> live? It's not like there's any point to it...

Correct, but in the case of IQ it's an artifical measurement system. So  
what was the basis of creating it? What, if any, problem was it designed  
to solve?

-- 
Phil Cook

--
I once tried to be apathetic, but I just couldn't be bothered
http://flipc.blogspot.com


Post a reply to this message

From: Stephen
Subject: Re: Wahahahaha!
Date: 13 Nov 2007 11:10:01
Message: <web.4739cb306f9d6136726bd13c0@news.povray.org>
"Phil Cook" <phi### [at] nospamrocainfreeservecouk> wrote:
> And lo on Tue, 13 Nov 2007 14:59:35 -0000, Invisible <voi### [at] devnull> did
> spake, saying:
>

> > Well, if you're going to put it that way... why are we bothering to be
> > live? It's not like there's any point to it...

Andrew, we bother to live because “life” does not like to be non-life. Most
people get some enjoyment out of it. Mind you sometime it can suck :(

> Correct, but in the case of IQ it's an artifical measurement system. So
> what was the basis of creating it? What, if any, problem was it designed
> to solve?
>


One of the biggest criticisms of IQ’s is that it has a high social content and
it is not portable between societies. As it was developed in the West it has a
bias towards western society.
I’ve found that the people that want to use IQs often tend to be people that do
well in the tests and want to promote their belief that they are special. Also
I’ve met quite a few people with high scores (they are not shy about telling
you) that I would not send out to buy a loaf of bread without a note.
Conversely I’ve met lots of people that have not done well in the tests or
failed in our education system but succeed in life (a much harder test IMO)
Just don’t get me started on psychometric testing. I have refused to sit them at
interviews.


Stephen


Post a reply to this message

From: Darren New
Subject: Re: Wahahahaha!
Date: 13 Nov 2007 11:28:37
Message: <4739d0b5$1@news.povray.org>
Invisible wrote:
> I guess the critical question is the SD...

I believe the SD is *supposed* to be 10, but that's more vague memory or 
heresay than me actually knowing.

-- 
   Darren New / San Diego, CA, USA (PST)
     Remember the good old days, when we
     used to complain about cryptography
     being export-restricted?


Post a reply to this message

From: Phil Cook
Subject: Re: Wahahahaha!
Date: 14 Nov 2007 06:51:19
Message: <op.t1r5kvo4c3xi7v@news.povray.org>
And lo on Tue, 13 Nov 2007 16:28:37 -0000, Darren New <dne### [at] sanrrcom>  
did spake, saying:

> Invisible wrote:
>> I guess the critical question is the SD...
>
> I believe the SD is *supposed* to be 10, but that's more vague memory or  
> heresay than me actually knowing.

Similarly I vaguely recall the need for renormalisation every decade with  
the average being about 3 points. So an IQ of 100 ten years later is only  
worth 97, wow you've suddenly got dumber and didn't even realise it :-P

-- 
Phil Cook

--
I once tried to be apathetic, but I just couldn't be bothered
http://flipc.blogspot.com


Post a reply to this message

<<< Previous 50 Messages Goto Initial 50 Messages

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.