public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "peter.mckinna at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug m3/27049] gdb crashes when printing variable of 2 dimensional dynamic array
Date: Fri, 11 Dec 2020 22:34:44 +0000	[thread overview]
Message-ID: <bug-27049-4717-so0OLwesED@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27049-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27049

--- Comment #3 from peter mckinna <peter.mckinna at gmail dot com> ---
HI,

  Thanks for the quick response. I was going to reply to simark that it's
quite difficult to
build a demo as I'm working on llvm debug generation and you would have to
build
llvm from source then apply a patch and then build cm3 from source. All of
which
is time consuming and tricky.

I can attach a minimal executable for running on Linux plus generated llvm
IR
and assembly output - total gziped size of about 2.2 M.

Hope that would suffice.

Regards Peter

On Sat, 12 Dec 2020 at 01:16, tromey at sourceware dot org <
sourceware-bugzilla@sourceware.org> wrote:

> https://sourceware.org/bugzilla/show_bug.cgi?id=27049
>
> Tom Tromey <tromey at sourceware dot org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |tromey at sourceware dot
> org
>
> --- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
> Maybe just attaching a minimal reproducing executable with debuginfo,
> with instructions for running it, would be good enough.
>
> --
> You are receiving this mail because:
> You reported the bug.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-12-11 22:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11  0:56 [Bug m3/27049] New: " peter.mckinna at gmail dot com
2020-12-11  4:45 ` [Bug m3/27049] " simark at simark dot ca
2020-12-11 14:16 ` tromey at sourceware dot org
2020-12-11 22:34 ` peter.mckinna at gmail dot com [this message]
2020-12-11 23:15 ` peter.mckinna at gmail dot com
2020-12-12  5:49 ` simark at simark dot ca
2020-12-15 18:19 ` tromey at sourceware dot org
2020-12-15 18:23 ` tromey at sourceware dot org
2020-12-15 18:24 ` tromey at sourceware dot org
2020-12-15 21:16 ` peter.mckinna at gmail dot com
2020-12-16 11:24 ` andrew.burgess at embecosm dot com
2020-12-17 17:30 ` andrew.burgess at embecosm dot com
2020-12-18  1:19 ` peter.mckinna at gmail dot com
2020-12-18  6:34 ` peter.mckinna at gmail dot com
2020-12-18 11:12 ` andrew.burgess at embecosm dot com

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=bug-27049-4717-so0OLwesED@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).