can't step over libvlc_new() in debug mode

[lxndr]

Hi,

can someone please help with this problem:
I did just start to use libVLC and my very simple application already works fine calling libVLC when executing it. Everything is good as long as I run my program and do not debug it. If I am debugging, I can step forward to the line with libvlc_new(), but libvlc_new() never returns. Other library functions like libvlc_get_version() do work.
Did I miss something to configure?

My system: I am working with Win10, Netbeans, C (gcc), MinGW (all 64Bit) and libVLC containted in this file http://download.videolan.org/vlc/last/win64/vlc-3.0.6-win64.7z

Thanks in advance!

Best regards

Alexander

[mfkl]

Logs?

What if you put the breakpoint after libvlc_new()?

[lxndr]

Logs?

Unfortunately I am not experienced with libvlc, but I think it's not possible to get logs at that stage of program execution.

On the one hand I should get logs by a parameter to libvlc_new():

Code: Select all

char const *debugVLC_argv[] = { "--file-logging", "--logfile=libvlc_log.txt", "--logmode=text", "--log-verbose=3" }; int debugVLC_argc = sizeof (debugVLC_argv) / sizeof (*debugVLC_argv); info->libvlc = libvlc_new(debugVLC_argc, debugVLC_argv);

If I run this the log is being printed, but not when debugging.

On the other hand I could use libvlc_log_set(), but this function needs a libvlc_instance_t* as parameter, which is however being returned by libvlc_new().

What if you put the breakpoint after libvlc_new()?

That's just the same. The program never reaches the breakpoint.

I am wondering what could cause such behaviour. Perhaps something in my system, but I am surely not the only one using that configuration.
Does libvlc_new() access/initialize any hardware (for acceleration)?