Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Franck Jullien <franck.jullien@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>, gdb@sourceware.org
Subject: Re: Lot of FAILs with gdb.base/structs.exp
Date: Wed, 13 Feb 2013 13:23:00 -0000	[thread overview]
Message-ID: <CAJfOKBxzYsaBsOMNK=4qF6RpRBuWZq4+K95sOX1iundrdsDObg@mail.gmail.com> (raw)
In-Reply-To: <511B6FD8.10607@redhat.com>

2013/2/13 Pedro Alves <palves@redhat.com>:
> On 02/13/2013 10:18 AM, Franck Jullien wrote:
>> Do you have any advice on the investigation method you'd use with a
>> program exiting like this ?:
>
> ...
>
>> (gdb) PASS: gdb.base/structs.exp: p chartest
>> ptype foo1
>> type = struct struct1 {
>>     tc a;
>> }
>> (gdb) PASS: gdb.base/structs.exp: ptype foo1; structs-tc
>> p/c fun1()
>> [Inferior 1 (process 42000) exited with code 0400]
>> The program being debugged exited while in a function called from GDB.
>
> So you have some kind of bug in your inferior function call
> implementation.  For some reason gdb doesn't regain control
> after the call ends.  At this point I'd just switch to reproducing
> the problem manually while debugging gdb, and try to figure
> things out.
> Did this work with 7.2?  That should make things easier,
> as you have a basis to compare.  Maybe something to do
> with the fact that we now default to putting the call
> dummy on stack, while it would go on entry before.
>
> --
> Pedro Alves
>

Ok, thank you guys. I'd say it works with GDB 7.2 but I have to double check.
I'll see what I can find and will keep you informed.

Franck.


      reply	other threads:[~2013-02-13 13:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 23:02 Franck Jullien
2013-02-13  2:59 ` Sergio Durigan Junior
     [not found]   ` <CAJfOKBxPQJhfc_kT_3m2OQTu-AHqr=fjA66EVD=3Z9_P1gQJOw@mail.gmail.com>
2013-02-13  7:35     ` Sergio Durigan Junior
2013-02-13 10:18       ` Franck Jullien
2013-02-13 11:09         ` Sergio Durigan Junior
2013-02-13 11:24         ` Pedro Alves
2013-02-13 13:23           ` Franck Jullien [this message]

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='CAJfOKBxzYsaBsOMNK=4qF6RpRBuWZq4+K95sOX1iundrdsDObg@mail.gmail.com' \
    --to=franck.jullien@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=palves@redhat.com \
    --cc=sergiodj@redhat.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