On 09/05/2018 05:30 PM, Richard W.M. Jones wrote:
It gives an odd error (see attached). Is that a bug in eu-stack?
It seems that all debuginfo was successfully loaded. I don't see a way
to debug this further. If it does not reproduce, I'm inclined to blame
it on faulty memory. 8-p
On Wed, 2018-09-05 at 18:04 +0100, Richard W.M. Jones wrote:
> On Wed, Sep 05, 2018 at 06:40:47PM +0200, Mark Wielaard wrote:
> > We don't know the exact release version, but given the build-id
> > [0aea4b30d53d7cc6386f1773a8dc8972793def1a] we should be able to
> > match it against an older glibc
On Wed, Sep 05, 2018 at 06:04:27PM +0100, Richard W.M. Jones wrote:
> On Wed, Sep 05, 2018 at 06:40:47PM +0200, Mark Wielaard wrote:
> > We don't know the exact release version, but given the build-id
> > [0aea4b30d53d7cc6386f1773a8dc8972793def1a] we should be able to
> > match it against an older
On Wed, Sep 05, 2018 at 06:40:47PM +0200, Mark Wielaard wrote:
> We don't know the exact release version, but given the build-id
> [0aea4b30d53d7cc6386f1773a8dc8972793def1a] we should be able to
> match it against an older glibc package.
Here are all the versions of glibc installed on that
On Wed, Sep 05, 2018 at 06:40:47PM +0200, Mark Wielaard wrote:
> On Wed, Sep 05, 2018 at 04:30:59PM +0100, Richard W.M. Jones wrote:
> > On Wed, Sep 05, 2018 at 05:23:45PM +0200, Mark Wielaard wrote:
> > > On Wed, 2018-09-05 at 13:59 +0100, Richard W.M. Jones wrote:
> > > > On Wed, Sep 05, 2018 at
On Wed, Sep 05, 2018 at 04:30:59PM +0100, Richard W.M. Jones wrote:
> On Wed, Sep 05, 2018 at 05:23:45PM +0200, Mark Wielaard wrote:
> > On Wed, 2018-09-05 at 13:59 +0100, Richard W.M. Jones wrote:
> > > On Wed, Sep 05, 2018 at 02:27:44PM +0200, Florian Weimer wrote:
> > > > But which one? For
On Wed, Sep 05, 2018 at 05:23:45PM +0200, Mark Wielaard wrote:
> On Wed, 2018-09-05 at 13:59 +0100, Richard W.M. Jones wrote:
> > On Wed, Sep 05, 2018 at 02:27:44PM +0200, Florian Weimer wrote:
> > > But which one? For 2.28-9.fc29 or 2.27.9000-35.fc29? If GDB can't
> > > find the build ID, I'd
On Wed, 2018-09-05 at 13:59 +0100, Richard W.M. Jones wrote:
> On Wed, Sep 05, 2018 at 02:27:44PM +0200, Florian Weimer wrote:
> > But which one? For 2.28-9.fc29 or 2.27.9000-35.fc29? If GDB can't
> > find the build ID, I'd suggest try the other version as well.
>
> Oh I see, good point. I
On Wed, Sep 05, 2018 at 02:27:44PM +0200, Florian Weimer wrote:
> On 09/05/2018 02:22 PM, Richard W.M. Jones wrote:
> >On Wed, Sep 05, 2018 at 02:10:15PM +0200, Florian Weimer wrote:
> >>On 09/05/2018 02:07 PM, Richard W.M. Jones wrote:
> >>>I just hit a weird bug. When I typed:
> >>>
> >>> $
On 09/05/2018 02:22 PM, Richard W.M. Jones wrote:
On Wed, Sep 05, 2018 at 02:10:15PM +0200, Florian Weimer wrote:
On 09/05/2018 02:07 PM, Richard W.M. Jones wrote:
I just hit a weird bug. When I typed:
$ sudo dnf update --best /mntsc
bash exited (and with it, my ssh session) saying:
On Wed, Sep 05, 2018 at 02:10:15PM +0200, Florian Weimer wrote:
> On 09/05/2018 02:07 PM, Richard W.M. Jones wrote:
> >I just hit a weird bug. When I typed:
> >
> > $ sudo dnf update --best /mntsc
> >
> >bash exited (and with it, my ssh session) saying:
> >
> > *** stack smashing detected
On 09/05/2018 02:07 PM, Richard W.M. Jones wrote:
I just hit a weird bug. When I typed:
$ sudo dnf update --best /mntsc
bash exited (and with it, my ssh session) saying:
*** stack smashing detected ***: terminated
Connection to srv closed.
This was after updating to
I just hit a weird bug. When I typed:
$ sudo dnf update --best /mntsc
bash exited (and with it, my ssh session) saying:
*** stack smashing detected ***: terminated
Connection to srv closed.
This was after updating to glibc-2.28-9.fc29.x86_64.
Unfortunately I cannot seem to reproduce it
13 matches
Mail list logo
