Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Ömer Sinan Ağacan" <omeragacan@gmail.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb <gdb@sourceware.org>
Subject: Re: Buildling gdb on Ubuntu 18.04
Date: Thu, 31 Jan 2019 06:23:00 -0000	[thread overview]
Message-ID: <CAMQQO3nYcxW-depU3cbN-dvFzL2AjT+n3dHTdqE2jOfgN0o=2A@mail.gmail.com> (raw)
In-Reply-To: <a3a92a2dcf059a1596d7a5db8c92c8c6@polymtl.ca>

> Which bug are you referring to?  Is it something know and documented in
> Bugzilla?

I don't of if any of these are documented in Bugzilla, but

- gdb sometimes prints more than one newline after a record. According to
  section 27.2.2 there should be only one newline.

- According to 27.2.2 a sequence of records result records should come after
  out-of-band record, but I sometimes get a sequence like [out-of-bound,
  result, out-of-bound].

- According to 27.2.2 a sequence of records should terminate with "(gdb)\n" or
  "(gdb)\r\n", but I get "(gdb) \n".

- Most annoyingly, when I add a breakpoint to a location that corresponds to
  multiple locations in the source code (so it leads to adding more than one
  breakpoint), the mi syntax gdb prints looks like this

      =breakpoint-created,bkpt={...},{...},{...}

  which is not valid because a "result" should look like `x=y` so stuff after
  the first "result" (`bkpt={...}`) are not actually results.

Ömer

Simon Marchi <simon.marchi@polymtl.ca>, 30 Oca 2019 Çar, 23:01
tarihinde şunu yazdı:
>
> On 2019-01-30 14:45, Ömer Sinan Ağacan wrote:
> > Interesting, I was also able to build in a docker container and it
> > works when I
> > copy the executable to the host system, so my problem is kind of
> > solved. I'm
> > still wondering what's wrong with my system though ...
> >
> > (Too bad the bug exists in the development version too so I have to
> > deal with it
> > in my application...)
>
> Sorry for not being able to help you for your build issue, it looks like
> a one off weird thing with your setup (with enough digging one would
> probably find it).
>
> Which bug are you referring to?  Is it something know and documented in
> Bugzilla?
>
> Simon


  reply	other threads:[~2019-01-31  6:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30  7:41 Ömer Sinan Ağacan
2019-01-30 14:58 ` Simon Marchi
2019-01-30 15:12   ` Ömer Sinan Ağacan
2019-01-30 15:50     ` Simon Marchi
2019-01-30 19:45       ` Ömer Sinan Ağacan
2019-01-30 20:01         ` Simon Marchi
2019-01-31  6:23           ` Ömer Sinan Ağacan [this message]
2019-01-31 15:54             ` Simon Marchi

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='CAMQQO3nYcxW-depU3cbN-dvFzL2AjT+n3dHTdqE2jOfgN0o=2A@mail.gmail.com' \
    --to=omeragacan@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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