 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nicolas Alvarez wrote:
>> (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...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Stephen wrote:
You're not the only one. In fact, I'm going to go out on a limb here and
say you're not the only one by a large measure...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Nicolas Alvarez wrote:
>>> (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...
Load a core dump on a debugger along with the executable containing
debugging info and the sourcecode, and you can pinpoint the line of code
that caused the crash, and see the contents of variables at the moment
of the crash. That's why coredumps are so big sometimes, they contain
all of the process's memory.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nicolas Alvarez wrote:
>> Nicolas Alvarez wrote:
>>>> (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...
>
> Load a core dump on a debugger along with the executable containing
> debugging info and the sourcecode, and you can pinpoint the line of code
> that caused the crash, and see the contents of variables at the moment
> of the crash. That's why coredumps are so big sometimes, they contain
> all of the process's memory.
You mean even though the memory layout is completely different every
time the program is run, the debugger can somehow work out which octet
means what?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Orchid XP v7 <voi### [at] dev null> wrote:
> > The original programmer with access to the sourcecode *can* deduce data
> > from it.
> I seriously doubt it...
Why?
What do you think the core file is for?
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Orchid XP v7 <voi### [at] devnull> wrote:
> You mean even though the memory layout is completely different every
> time the program is run, the debugger can somehow work out which octet
> means what?
No, programs just dump core for the fun of it, without it having any
use or benefit.
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
> Orchid XP v7 <voi### [at] devnull> wrote:
>>> The original programmer with access to the sourcecode *can* deduce data
>>> from it.
>
>> I seriously doubt it...
>
> Why?
>
> What do you think the core file is for?
A last-ditch attempt to do something useful?
I mean, if you're the guy who designed the inside of the C compiler and
knows the exact instruction scheduling algorithm that it uses *and* you
somehow have access to the source code version of the program *and* you
understand the exact execution path that lead to this point *and* you're
a super-expert in extremely low-level programming *and* you have insane
amounts of time available... yeah, theoretically you might possibly be
able to glean a few tiny bits of info from it. But really, for anything
other than a HelloWorld program, you're not going to get much of use out
of it. (Heck, the crash probably isn't even anywhere near where the bug
is...)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Warp wrote:
>> What do you think the core file is for?
>
> A last-ditch attempt to do something useful?
Developers ask users to send core dumps when something crashes, so I
guess it's useful.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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.
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 08 Nov 2007 18:39:12 +0000, Orchid XP v7 wrote:
> You mean even though the memory layout is completely different every
> time the program is run, the debugger can somehow work out which octet
> means what?
Yes, absolutely.
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
