Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Micol Ponce <dmp18@alu.ua.es>
To: mec.gnu@mindspring.com, gdb@sources.redhat.com
Subject: Re: gdb segmentation fault
Date: Wed, 14 Jan 2004 16:46:00 -0000	[thread overview]
Message-ID: <1074098755.9144.2.camel@DMICOL.MICOLPONCE> (raw)
In-Reply-To: <20040114093241.92DB64B104@berman.michael-chastain.com>

[-- Attachment #1: Type: text/plain, Size: 858 bytes --]

Hi,

Here I sent you the typescript file that I generated doing what you told
me. I hope you can find the bug.

Sincerely,

  Daniel Micol Ponce

El mié, 14-01-2004 a las 10:32, Michael Elizabeth Chastain escribió:
> Hello,
> 
> This sounds like a real bug in gdb.
> 
> Can you do this please:
> 
>   Run the "script" command
>   Run "env" so I can see your environment
>     (particularly the locale settings)
>   Do "gdb gdb"
>   Make the bug happen
>   Get a backtrace
>   Exit "script"
> 
> Then mail me the same information that you mailed to bug-gdb,
> along with the whole "typescript" file.
> 
> Send it to:
> 
>   mec.gnu@mindspring.com (my other e-mail address)
>   gdb@sources.redhat.com (the current mailing list)
> 
> I know this is a lot of work to ask of you, but it will help me
> localize the bug.
> 
> Thanks,
> 
> Michael C
> GDB QA Guy

[-- Attachment #2: typescript --]
[-- Type: application/octet-stream, Size: 4731 bytes --]

       reply	other threads:[~2004-01-14 16:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040114093241.92DB64B104@berman.michael-chastain.com>
2004-01-14 16:46 ` Daniel Micol Ponce [this message]
2004-01-15 14:50   ` Daniel Jacobowitz
2004-01-27  7:25 Michael Elizabeth Chastain
  -- strict thread matches above, loose matches on Subject: below --
1998-06-22  6:35 GDB " Konrad Bernloehr
1998-06-29  2:23 ` Peter.Schauer

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=1074098755.9144.2.camel@DMICOL.MICOLPONCE \
    --to=dmp18@alu.ua.es \
    --cc=daniel.micol@unix.net \
    --cc=gdb@sources.redhat.com \
    --cc=mec.gnu@mindspring.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