Hi Riccardo,
thanks for your observations!
Looks like finally found the root cause for making GWorkspace
malfunction on i386!
On 11/19/24 11:29, Riccardo Mottola wrote:
I see something very strange. As information, do you have the Content
Inspector open? I suppose not.. in case don't.
I don't
Thank you Yavor for this patch. It looks correct to me and should resolve this
specific issue. As for the code in the whole Address framework it will need a
lot more of cleanup. Just skimming over it I noticed dozens of issues. i am
quite surprised that this code does anything useful at all. If
Yavor,
you really did it!
On 11/20/24 02:23, Yavor Doganov wrote:
Please test the attached patch (it solves the problem for me):
$ apt-get source addresses-for-gnustep && cd addresses-for-gnustep-*
(Make sure it's 0.4.8-5; the trixie/sid version)
$ cp /path/to/1087735.patch debian/patches
$ ech
Control: reassign -1 libaddressview0 0.4.8-5
Control: retitle -1 [i386] VCFViewer inspector aborts GWorkspace, making it
unusable
Control: affects -1 gworkspace.app
Control: tags -1 + patch
Paul Seelig wrote:
> Looks like finally found the root cause for making GWorkspace
> malfunction on i386!
Hi Riccardo,
now let's hope the VCF Inspector can be fixed somehow.
On 11/20/24 01:30, Riccardo Mottola wrote:
it is very likely that you nailed it to this VCF Inspector!
now.. many things could be. The source code has a bug or bitrotted.
It was not rebuilt properly, ecc,
I suppose this is th
Hi Paul,
Paul Seelig wrote:
Unless i am not utterly mistaken, then the debugging should probably
rather continue with 'addresses-for-gnustep'.
it is very likely that you nailed it to this VCF Inspector!
now.. many things could be. The source code has a bug or bitrotted.
It was not rebuilt pro
Hi,
I see something very strange. As information, do you have the Content
Inspector open? I suppose not.. in case don't.
#7 0xb74592d3 in -[NSObject doesNotRecognizeSelector:] (self=0x395e940,
_cmd=0xb780ac48 <_OBJC_SELECTOR_TABLE+264>, aSelector=0xb7db3b78
<_OBJC_SELECTOR_TABLE+312>)
Paul Seelig wrote:
> The screenshot provided is from a bookworm system with the
> backported GNUstep packages from trixie.
Oh, I missed this. A "backport" means to rebuild the package for an
older distro release using the toolchain of the older release, and
older versions of the build-dependencie
On 11/18/24 22:24, Yavor Doganov wrote:
Paul Seelig wrote:
The screenshot provided is from a bookworm system with the
backported GNUstep packages from trixie.
Oh, I missed this. A "backport" means to rebuild the package for an
older distro release using the toolchain of the older release, and
On 11/18/24 22:02, Yavor Doganov wrote:
Continuing.
Thanks but this is not useful. When you hit the breakpoint, type
"bt" at the GDB prompt, not "c".
This time i set up a fresh system installation using a
debian-12.8.0-i386-netinst.iso which was subsequently dist-upgraded to
trixie.
This was to
Hi,
FWIW, I also cannot reproduce on i386, but this is on a bookworm
machine with manually built latest GNUstep + GWorkspace from tarballs;
GCC 12.2.0. The OP reports the bug on trixie, GCC 14.2.0.
I use Devuan and also have 12.2 compiler, so I think we are matched here.
On another system (64
Paul Seelig wrote:
> On 11/18/24 07:55, Yavor Doganov wrote:
> > (gdb) bt
> >
> > And then post the backtrace you get? Thanks!
> Breakpoint 1, -[NSException raise] (self=0x3849d20,
> _cmd=0xb77db730 <_OBJC_SELECTOR_TABLE+240>) at ./Source/NSException.m:1599
> warning: 1599 ./Source/NSExcept
On 11/18/24 07:55, Yavor Doganov wrote:
Control: severity -1 grave
Control: tags -1 + moreinfo
Paul Seelig wrote:
[ snip ]
A screenshot is available at
http://wmlive.rumbero.org/NSInvalidArgumentException.png for a
visual depiction of the error message.
This shows NSContstantString(instance)
Hi Riccardo,
Riccardo Mottola via pkg-GNUstep-maintainers wrote:
> is the issue reproducible on a system you have on where you can get a
> stacktrace?
I already asked Paul for a backtrace (see
https://bugs.debian.org/1087735).
> I just tested on my Linux i386 laptop running Devuan with GCC runti
Hello Paul,
is the issue reproducible on a system you have on where you can get a
stacktrace?
I just tested on my Linux i386 laptop running Devuan with GCC runtime
(all source being GIT and compiled by myself, no packages) and I have no
issues with GWorkspace. So no immediate i386 32bit issu
Control: severity -1 grave
Control: tags -1 + moreinfo
Paul Seelig wrote:
> Package: gworkspace.app
> Version: 1.0.0-4
> Severity: important
>
> the current gworkspace.app application for trixie/i386 shows following error
> message when started:
>
> "Uncaught exception NSInvalidArgumentException
Package: gworkspace.app
Version: 1.0.0-4
Severity: important
Tags: upstream
X-Debbugs-Cc: discuss-gnus...@gnu.org, wml...@sf.net, wml...@rumbero.org
Hello all,
the current gworkspace.app application for trixie/i386 shows following error
message when started:
"Uncaught exception NSInvalidArgument
17 matches
Mail list logo