public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Mathew Yeates <mat.yeates@gmail.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: help with loading core files
Date: Thu, 22 Jul 2010 17:55:00 -0000	[thread overview]
Message-ID: <AANLkTilVOGPt2T_yF-vH9s3xAsFridRw70VvZ2PWnp7n@mail.gmail.com> (raw)
In-Reply-To: <4C48800B.1030100@vmware.com>

How do people deal with running to a breakpoint that takes 10 minutes
to get to? It would be great if I could run to the breakpoint once,
save some info, and in the future just return to the breakpoint and
keep running from there.

On Thu, Jul 22, 2010 at 10:29 AM, Michael Snyder <msnyder@vmware.com> wrote:
> None that I'm aware of, at least on Linux.
>
> Mathew Yeates wrote:
>>
>> bummer. Is there any way to do this? I assumed that the core file
>> contained enough information to resume processing.
>>
>>
>>>> Shouldn't I be able to continue my program from here? Instead, I get
>>>> "Program terminated with signal 5, Trace/breakpoint trap"
>>>> And I can't continue because I get
>>>> "The program is not being run."
>>>
>>> No, you can't resume running from a corefile.
>>>
>>>>  x86_64 x86_64 x86_64 GNU/Linux
>>>>
>>>>
>>>> On Thu, Jul 22, 2010 at 10:07 AM, Michael Snyder <msnyder@vmware.com>
>>>> wrote:
>>>>>
>>>>> Mathew Yeates wrote:
>>>>>>
>>>>>> Hi
>>>>>> I posted something about this earlier and I now have time to try and
>>>>>> figure this out.
>>>>>> When I run gdb myexe mycore
>>>>>> I get
>>>>>> Program terminated with signal 5, Trace/breakpoint trap.
>>>>>>
>>>>>> This is gdb-7.2.50.20100713.
>>>>>>
>>>>>> Any ideas for me to try? I'm no gdb guru but maybe I can generate info
>>>>>> usable  to someone.
>>>>>>
>>>>>> Mathew
>>>>>
>>>>> What signal do you believe your corefile should be reporting?
>>>>>
>>>>> What host and operating system are you running on?
>>>>>
>>>
>
>

  reply	other threads:[~2010-07-22 17:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-22 17:04 Mathew Yeates
2010-07-22 17:07 ` Michael Snyder
2010-07-22 17:16   ` Mathew Yeates
2010-07-22 17:26     ` Michael Snyder
2010-07-22 17:28       ` Mathew Yeates
2010-07-22 17:29         ` Michael Snyder
2010-07-22 17:55           ` Mathew Yeates [this message]
2010-07-22 18:07             ` Jan Kratochvil
2010-07-22 18:09               ` Michael Snyder
2010-07-22 18:14                 ` Mathew Yeates
2010-07-22 18:18                   ` Jan Kratochvil
2010-07-28  9:06                     ` Steffen Dettmer
2010-07-28 12:24                       ` Jan Kratochvil
2010-07-28  9:03             ` Steffen Dettmer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTilVOGPt2T_yF-vH9s3xAsFridRw70VvZ2PWnp7n@mail.gmail.com \
    --to=mat.yeates@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=msnyder@vmware.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).