On Sat, 2023-07-29 at 19:18 -0700, dchme...@gmail.com wrote:
>
> > Note the "debug_info, not stripped" part which indicates that the
> > binary contains debug symbol and variable names. [...]
> This time I edited pan.SlackBuild to not strip the binary and it's
> like
> you explained above. I ran
On 7/29/23 2:59 AM, Dominique Dumont wrote:
On Friday, 28 July 2023 07:33:10 CEST David Chmelik wrote:
I think it has them as I ran 'gdb --args pan --debug'. How do I get
line numbers then? I'm just a gdb beginner so could use full
instructions... Pan now doesn't always crash fast, but always
On Sat, 2023-07-15 at 22:20 -0700, dchme...@gmail.com wrote:
>
> The pan.SlackBuild uses these compiling flags '-O2 -fPIC'. Do any
> these
> conflict with '-Oo -g'?
Yes, '-O2' mean normal optimization, which mean, that compiled code is
optimized so, that compiled code may not point to source co
On Friday, 28 July 2023 07:33:10 CEST David Chmelik wrote:
> I think it has them as I ran 'gdb --args pan --debug'. How do I get
> line numbers then? I'm just a gdb beginner so could use full
> instructions... Pan now doesn't always crash fast, but always crashes.
Looks like the pan you compile
On 7/27/23 9:57 AM, Dominique Dumont wrote:
On Thursday, 27 July 2023 09:40:33 CEST dchme...@gmail.com wrote:
#0 0x76451ae7 in strtoll_l_internal () at /lib64/libc.so.6
#1 0x76444f90 in atoi () at /lib64/libc.so.6
#2 0x00733631 in pan::DataImpl::load_headers(pan::D
On Monday, 24 July 2023 09:44:05 CEST David Chmelik wrote:
> When I used those arguments/flags/switches and ran 'gdb pan' it said it
> has no debugging symbols. Below is the configure line from the SlackBuild.
>
> ./configure --prefix=/usr --localstatedir=/var/lib --sysconfdir=/etc
> --mandir=/us
On Thursday, 27 July 2023 09:40:33 CEST dchme...@gmail.com wrote:
> #0 0x76451ae7 in strtoll_l_internal () at /lib64/libc.so.6
> #1 0x76444f90 in atoi () at /lib64/libc.so.6
> #2 0x00733631 in pan::DataImpl::load_headers(pan::DataIO
> const&, pan::Quark const&) ()
ok
On 9/8/22 6:07 AM, Dominique Dumont wrote:
On Thursday, 8 September 2022 12:16:10 CEST David Chmelik wrote:
I compiled pan 0.151 but, after starting, quickly got another
segmentation fault.
Can you get a backtrace ? [...]
Thread 1 "pan" received signal SIGSEGV, Segmentation fault.
0x76
dchmelik-Re5JQEeQqe8AvxtiuMwx3w posted on Sat, 15 Jul 2023 22:20:08 -0700
as excerpted:
> On 7/13/23 12:57 PM, reijo.korho...@gmail.com wrote:
>> On Tue, 2023-07-11 at 18:56 -0700, David Chmelik wrote:
>>> Well, how do I do that? This command had no output: ./configure
>>> --help|grep -i debug .
On 7/19/23 9:31 AM, Dominique Dumont wrote:
On Thursday, 6 July 2023 10:24:45 CEST dchme...@gmail.com wrote:
Now I compiled 0.154. I don't know that I'll be able to get a
backtrace. Do I need debugging compiled in, and if so, how do I do that
then get the backtrace?
By default, pan is built w
On Thursday, 6 July 2023 10:24:45 CEST dchme...@gmail.com wrote:
> Now I compiled 0.154. I don't know that I'll be able to get a
> backtrace. Do I need debugging compiled in, and if so, how do I do that
> then get the backtrace?
By default, pan is built with with ' -g -O2 ' and the pan executabl
On 7/13/23 12:57 PM, reijo.korho...@gmail.com wrote:
On Tue, 2023-07-11 at 18:56 -0700, David Chmelik wrote:
Well, how do I do that? This command had no output: ./configure
--help|grep -i debug .
My answer is again very generic.
Hmm... Is your target to debug pan. What your have done before?
On Tue, 2023-07-11 at 18:56 -0700, David Chmelik wrote:
> Well, how do I do that? This command had no output: ./configure
> --help|grep -i debug .
My answer is again very generic.
Hmm... Is your target to debug pan. What your have done before? If you
run "./configure", this command is normally
On 7/7/23 11:51 AM, reijo.korho...@gmail.com wrote:
On Thu, 2023-07-06 at 01:24 -0700, dchme...@gmail.com wrote:
On 9/8/22 6:07 AM, Dominique Dumont wrote:
On Thursday, 8 September 2022 12:16:10 CEST David Chmelik wrote:
I compiled pan 0.151 but, after starting, quickly got another
segmentatio
On Thu, 2023-07-06 at 01:24 -0700, dchme...@gmail.com wrote:
> On 9/8/22 6:07 AM, Dominique Dumont wrote:
> > On Thursday, 8 September 2022 12:16:10 CEST David Chmelik wrote:
> > > I compiled pan 0.151 but, after starting, quickly got another
> > > segmentation fault.
> > Can you get a backtrace? [
On 9/8/22 6:07 AM, Dominique Dumont wrote:
On Thursday, 8 September 2022 12:16:10 CEST David Chmelik wrote:
I compiled pan 0.151 but, after starting, quickly got another
segmentation fault.
Can you get a backtrace? [...]
Now I compiled 0.154. I don't know that I'll be able to get a
backtrac
On Thursday, 1 December 2022 03:54:24 CET dchme...@gmail.com wrote:
> On 9/8/22 6:07 AM, Dominique Dumont wrote:
> > On Thursday, 8 September 2022 12:16:10 CEST David Chmelik wrote:
> >> I compiled pan 0.151 but, after starting, quickly got another
> >> segmentation fault.
> >
> > Can you get a ba
On 9/8/22 6:07 AM, Dominique Dumont wrote:
On Thursday, 8 September 2022 12:16:10 CEST David Chmelik wrote:
I compiled pan 0.151 but, after starting, quickly got another
segmentation fault.
Can you get a backtrace ? [...]
How?
___
Pan-users mailing
On Thu, 8 Sep 2022 03:16:10 -0700, David Chmelik wrote:
> Thanks! GitLab obviously isn't made for people who don't use git and
> just want to test; I'd have never found that and probably still won't be
> able to find tarballs later.
Just remember that "Tags" is the place to look - or bookmark the
On Thursday, 8 September 2022 12:16:10 CEST David Chmelik wrote:
> I compiled pan 0.151 but, after starting, quickly got another
> segmentation fault.
Can you get a backtrace ?
All the best
___
Pan-users mailing list
Pan-users@nongnu.org
https://lis
On 9/8/22 1:00 AM, Dominique Dumont wrote:
On Thursday, 8 September 2022 01:25:16 CEST David Chmelik wrote:
[...] But you can get tarballs on this gitlabpage:
https://gitlab.gnome.org/GNOME/pan/-/tags
Each version has a button to download source on the right.
For instance:
https://gitlab.gno
On Thursday, 8 September 2022 01:25:16 CEST David Chmelik wrote:
> Aren't
> easily-accessible/properly-numbered 0.150 & 0.151 tarballs going to be
> released on pan.rebelbase.com?
I don't think so.
But you can get tarballs on this gitlabpage:
https://gitlab.gnome.org/GNOME/pan/-/tags
Each ver
On 9/6/22 1:26 AM, Duncan wrote:
dchmelik-Re5JQEeQqe8AvxtiuMwx3w posted on Sun, 4 Sep 2022 21:43:11 -0700
as excerpted:
On 9/4/22 5:19 AM, Duncan wrote:
dchmelik-Re5JQEeQqe8AvxtiuMwx3w posted on Fri, 2 Sep 2022 19:37:53
-0700 as excerpted:
Like for past few years until earlier this year, pan
dchmelik-Re5JQEeQqe8AvxtiuMwx3w posted on Sun, 4 Sep 2022 21:43:11 -0700
as excerpted:
> On 9/4/22 5:19 AM, Duncan wrote:
>> dchmelik-Re5JQEeQqe8AvxtiuMwx3w posted on Fri, 2 Sep 2022 19:37:53
>> -0700 as excerpted:
>>
>>> Like for past few years until earlier this year, pan always crashes
>>> fast
On 9/4/22 5:19 AM, Duncan wrote:
Pan version 0.151, "Butcha", was released in late June. That should have
most of the fixes and be pretty stable (tho a quick look says there's more
than translations committed since then, but I'd say I've been stable since
about then or a bit earlier), but given
On 9/4/22 5:19 AM, Duncan wrote:
dchmelik-Re5JQEeQqe8AvxtiuMwx3w posted on Fri, 2 Sep 2022 19:37:53 -0700
as excerpted:
Like for past few years until earlier this year, pan always crashes fast
again (on Slackware64 15+current GNU/Linux).
Pan always says something like this before crashing: (pa
dchmelik-Re5JQEeQqe8AvxtiuMwx3w posted on Fri, 2 Sep 2022 19:37:53 -0700
as excerpted:
> Like for past few years until earlier this year, pan always crashes fast
> again (on Slackware64 15+current GNU/Linux).
>
> Pan always says something like this before crashing: (pan:16759):
> Gtk-CRITICAL **
On 9/3/22 4:00 AM, Rhialto wrote:
On Fri 02 Sep 2022 at 19:37:53 -0700, dchme...@gmail.com wrote:
Like for past few years until earlier this year, pan always crashes fast
again (on Slackware64 15+current GNU/Linux).
Pan always says something like this before crashing: (pan:16759):
Gtk-CRITICAL
On Fri 02 Sep 2022 at 19:37:53 -0700, dchme...@gmail.com wrote:
> Like for past few years until earlier this year, pan always crashes fast
> again (on Slackware64 15+current GNU/Linux).
>
> Pan always says something like this before crashing: (pan:16759):
> Gtk-CRITICAL **: 19:23:47.724: IA__gtk_t
29 matches
Mail list logo
