On Feb 13, 8:21 am, Paul Pluzhnikov <[EMAIL PROTECTED]> wrote:
> Well, if you collect package/version info for all the DSOs in
> the process, you probably can fetch corresponding packages,
> and debug that core.
>
> Obviously you wouldn't be able to do that for "self-built"
> libraries. Depending o
"Bruno Gonzalez (STenyaK)" <[EMAIL PROTECTED]> writes:
>> Without matching shared libraries, gdb just uses whatever libraries
>> are installed on the current system, if these don't match what's
>> in the dump, you get "garbage".
>
> I see, thanks for the info. Unfortunately, that increases the cra
Hi Paul, thanks for the reply.
On Feb 12, 5:31 pm, Paul Pluzhnikov <[EMAIL PROTECTED]> wrote:
> This core dump came from uncaught exception (but you probably
> know that).
Yes, it was an intended crash.
> You aren't necessarily doing anything wrong.
>
> The core dump contains memory image of the
"Bruno Gonzalez (STenyaK)" <[EMAIL PROTECTED]> writes:
> I'm new to debugging using core dumps. I've managed to get core dumps
> + symbols using g++ and gdb under linux.
> I compile using g++ -g -dH, and i debug using gdb executableFile -c
> coredumpFile.
>
> This is a test program backtrace i
