Hi,
>Note: I didn't put an entry to close this bug because I intend to
>retitle it, lower the severity, and still look for a cause/fix. This
>seems better to me than closing the bug and opening a new one for follow
>up.
looks good to me, sponsored!
G:
I've prepared a new package and uploaded it to mentors:
https://mentors.debian.net/debian/pool/main/x/xerces-c/xerces-c_3.1.4+debian-2.dsc
If someone wants to test and/or upload it, I would appreciate it.
Note: I didn't put an entry to close this bug because I intend to
retitle it, lower the
On Fri, Dec 16, 2016 at 08:25:02AM +, Gianfranco Costamagna wrote:
> Hi,
>
>
> >export DEB_BUILD_MAINT_OPTIONS=noopt
>
> >
> >to the top of d/rules and rebuilding should do it.
>
>
> it worked:
> DEB_BUILD_OPTIONS=noopt dpkg-buildpackage
>
> [...]
>
Interesting. Under the emulator
Hi,
>export DEB_BUILD_MAINT_OPTIONS=noopt
>
>to the top of d/rules and rebuilding should do it.
it worked:
DEB_BUILD_OPTIONS=noopt dpkg-buildpackage
[...]
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/libxerces-c-samples/usr/bin/SAXPrint
On a whim, I decided to install the Hercules s390 emulator and see if I
could reproduce the problem there. It's slow (4+ hours to do a build of
xerces) but it appears to work, and the issue shows up there as well.
I started trying to trace down the memory issue in real time, but the
variables I
On Wed, Dec 14, 2016 at 07:11:12AM +, Gianfranco Costamagna wrote:
>
> >So while I'm not sure it will help, there might be benefit to try to get a
> >stack trace from DOMCount. It's possible there's an exception being
> >thrown but it's getting caught/squashed. If someone wants to try to
>So while I'm not sure it will help, there might be benefit to try to get a
>stack trace from DOMCount. It's possible there's an exception being
>thrown but it's getting caught/squashed. If someone wants to try to get
>a stack trace, the command will be
>
>libtool --mode=execute gdb --args
On Tue, Dec 13, 2016 at 11:15:26PM +, Gianfranco Costamagna wrote:
>
> http://paste.debian.net/902086/
>
> ^^ this is the file you requested
>
> G.
That's great. As I had hoped, ignoring that exception allows SAXCount
to complete successfully, and with the expected output (despite the
Hi,
>Was that the only exception? If so, that exception gets thrown (and
>handled) even on a successful run. In which case, can you post the
>test-results.log?
yes, the only one
(gdb) continue
Continuing.
samples/data/personal.xml: 40029473 ms (37 elems, 12 attrs, 134 spaces, 134
chars)
On Tue, Dec 13, 2016 at 12:06:46PM +, Gianfranco Costamagna wrote:
> Hi
>
>
> >Based on the stack trace, the exception is thrown because a managed
>
> >buffer that is being freed isn't actually registered to the buffer manager.
> >his shouldn't happen, since the only way to get a buffer is
Hi
>Based on the stack trace, the exception is thrown because a managed
>buffer that is being freed isn't actually registered to the buffer manager.
>his shouldn't happen, since the only way to get a buffer is to request
>it from the manager in the first place. It's possible there's a memory
Based on the stack trace, the exception is thrown because a managed
buffer that is being freed isn't actually registered to the buffer manager.
This shouldn't happen, since the only way to get a buffer is to request
it from the manager in the first place. It's possible there's a memory
>
> It still fails the very same way.
> Attached the backtrace I get with the way you said above (without
> exporting anything). It seems to really be full, what Gianfranco posted
> looks more like the non-full/regular bt, dunno why.
Thanks. Disregard my other email.
GDB didn't find the debug
On Sun, Dec 11, 2016 at 01:54:36PM -0500, Bill Blough wrote:
> On Sun, Dec 11, 2016 at 07:43:08PM +0100, Mattia Rizzolo wrote:
> > On Sun, Dec 11, 2016 at 01:34:18PM -0500, Bill Blough wrote:
> > > I just found a reference in the Debian Maintainer's Guide that says the
> > > default build locale
On Sun, Dec 11, 2016 at 07:43:08PM +0100, Mattia Rizzolo wrote:
> On Sun, Dec 11, 2016 at 01:34:18PM -0500, Bill Blough wrote:
> > I just found a reference in the Debian Maintainer's Guide that says the
> > default build locale is C. And it looks like the Ubuntu build is
> > explicitly setting a
On Sun, Dec 11, 2016 at 06:20:13PM +, Mattia Rizzolo wrote:
> anyhow, 1) build should not depend on the locale it runs
I'll admit, I don't know a lot about locales, etc., but some of the
tests use files in UTF-8. Wouldn't that generally require UTF-8 support
from the locale?
> 2) afaik it
On Sun, Dec 11, 2016 at 01:34:18PM -0500, Bill Blough wrote:
> I just found a reference in the Debian Maintainer's Guide that says the
> default build locale is C. And it looks like the Ubuntu build is
> explicitly setting a locale of C.UTF-8.
Where is that?
Really, in Debian there is no
On Sun, Dec 11, 2016 at 05:57:38PM +, Gianfranco Costamagna wrote:
> Hi,
>
> >Does anyone know (or can find out) the default locale on the s390
> >systems, and does that differ from the other architectures?
> >
> >env | egrep "(LC|LANG)"
> >
> >should give a list of relevant vars.
>
>
>
On Sun, Dec 11, 2016 at 6:57 PM Gianfranco Costamagna <
costamagnagianfra...@yahoo.it> wrote:
> (not sure if it is related to my laptop configuration, I did ssh and
> copy-pasted)
>
Yep, ssh transfers LC_* variables.
anyhow, 1) build should not depend on the locale it runs 2) afaik it isn't
any
Hi,
>Does anyone know (or can find out) the default locale on the s390
>systems, and does that differ from the other architectures?
>
>env | egrep "(LC|LANG)"
>
>should give a list of relevant vars.
(not sure if it is related to my laptop configuration, I did ssh and
copy-pasted)
Does anyone know (or can find out) the default locale on the s390
systems, and does that differ from the other architectures?
env | egrep "(LC|LANG)"
should give a list of relevant vars.
Thanks,
Bill
On Sat, Dec 10, 2016 at 08:56:29AM +, Gianfranco Costamagna wrote:
>
> > libtool --mode=execute gdb --args samples/SAXCount
> > samples/data/personal.xml
> > catch throw
> >
> > bt full
> >continue
> > quit
> >This will hopefully help me to isolate this issue.
> >
>
>
> here we are!
>
Hi,
>
> libtool --mode=execute gdb --args samples/SAXCount samples/data/personal.xml
> catch throw
>
> bt full
>continue
> quit
>This will hopefully help me to isolate this issue.
>
here we are!
http://paste.debian.net/901516/
G.
On Sat, Dec 10, 2016 at 02:25:08AM +0100, Mattia Rizzolo wrote:
> On Fri, Dec 09, 2016 at 08:11:54PM -0500, Bill Blough wrote:
> > > >Or does anyone have other suggestions?
>
> I have one: please try to CC people (and/or MLs) sooner. I now noticed
> that you asked for help more than one month
On Fri, Dec 09, 2016 at 08:11:54PM -0500, Bill Blough wrote:
> > >Or does anyone have other suggestions?
I have one: please try to CC people (and/or MLs) sooner. I now noticed
that you asked for help more than one month ago, but I wasn't aware of
that at all. And now the freeze is hovering upon
On Fri, Dec 09, 2016 at 11:07:54PM +, Gianfranco Costamagna wrote:
> >Can anyone comment on the use of -Bsymbolic_functions in Ubuntu? If I
> >understand it correctly, it shouldn't have any effect on this, but I
> >have no way to test it other than another upload.
>
>
> I still prefer the
Hi Bill,
>I'd really like to get this resolved before the freeze.
>
>Can anyone comment on the use of -Bsymbolic_functions in Ubuntu? If I
>understand it correctly, it shouldn't have any effect on this, but I
>have no way to test it other than another upload.
I still prefer the default -Ofoo
I'd really like to get this resolved before the freeze.
Can anyone comment on the use of -Bsymbolic_functions in Ubuntu? If I
understand it correctly, it shouldn't have any effect on this, but I
have no way to test it other than another upload.
Assuming that's not it, would someone be willing
Hi,
> > Hey William, did you have a chance to look at this bug? i couldnt find
> > much on the upstream bug tracker but there is also a 3.1.4 new release
> > you might want to test if fixes this bug else report it upstream.
> > thanks!!
the new release didn't work, but the same build worked on
I looked at it briefly, but had to refocus on other issues before I
could really get anywhere. I'll get it sorted out and/or forwarded
shortly.
Thanks for the ping!
On Thu, Nov 03, 2016 at 04:10:27PM -0400, Sandro Tosi wrote:
> On Mon, 8 Aug 2016 13:24:48 + Mattia Rizzolo
On Mon, 8 Aug 2016 13:24:48 + Mattia Rizzolo wrote:
> source: xerces-c
> version: 3.1.3+debian-2.1
> severity: serious
>
> Dear maintainer,
>
> your package failed to build on buildds on the s390x architecure only
> during a rebuild for the transition to icu57, using gcc6
31 matches
Mail list logo