Hi Robert,
you could eithe rtry to run it within gdb and get a backtrace and/or
look at the output of dmesg, sometimes it says which library is the
reason of your issues or whats going on.
>From my experience running memtest might be an idea, too :)
cheers,
bernd
On 06/14/2015 10:10 AM, Robert Latest wrote:
> Hello viking maintainer,
>
> I just did a very primitive test. I downloaded the Debian viking source
> and built it natively on my system. Still segfaults. Then I replaced
> main() with a primitive two-liner (see below), and it still segfaults.
> So the error is within some start-up code or linker settings, but not
> the actual viking code. Unfortunately such issues are well beyond my
> programming skills so I don't know where to look next.
>
> BTW I love viking, and I use it daily. Otherwise I wouldn't be
> pestering you like this. Thanks for maintaining such a great piece of
> software.
>
> /* Just a test */
> int main( int argc, char *argv[] ) {
> fprintf(stderr, "MAIN\n");
> return 0;
> }
>
> /* original main() */
> int main1( int argc, char *argv[] )
> {
> VikWindow *first_window;
> GdkPixbuf *main_icon;
> gboolean dashdash_already = FALSE;
> /* .... remaining code ...*/
>
--
Bernd Zeimetz Debian GNU/Linux Developer
http://bzed.de http://www.debian.org
GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
