Buildling gdb on Ubuntu 18.04

Ömer Sinan Ağacan omeragacan@gmail.com
Thu Jan 31 06:23:00 GMT 2019


> 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



More information about the Gdb mailing list